1 / 28

FDIR Spacecraft fault protection system

Project 1 Problem understanding & UI design. FDIR Spacecraft fault protection system. Euro Team Alauzet Pierre, Ahvenniemi Mikko, Colin Julien, Starck Benoit. CS554 - Design for Software & Systems. Table of Contents. Problem understanding Functional requirements (use-case model)

alcina
Download Presentation

FDIR Spacecraft fault protection system

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project 1 Problemunderstanding & UI design FDIRSpacecraftfault protection system Euro Team Alauzet Pierre, Ahvenniemi Mikko, Colin Julien, Starck Benoit CS554 - Design for Software & Systems

  2. Table of Contents • Problemunderstanding • Functionalrequirements (use-case model) • Non-functionalrequirements • Usabilityanalysis & design

  3. 1. Problemunderstanding Business purpose & problem frames Problem understanding Functional requirements (use-case model) Non-functional requirements Usability analysis & design

  4. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Business purpose & requirements • Fault Detection, Isolation and Recovery (FDIR) system is monitoring systems for spacecraft. • FDIR • Guarantee the completion of any time critical activities • Providemanual control • Display information continuously • Collect data to data storage • Locate the fault • Store irresolvable conditions in reports • Automaticrecovery to failure • Keep the control with safety, observability & commandability

  5. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Problem frames Ground Control • Context Diagram : Crew Systems FDIR Information Display Report FDIR Storage System

  6. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Problem frames (cont.) • Problemdiagram 1/2: Display information continuously Information display a d FDIR Display information c b Systems b: Systems!{functionnal/not funct. proper./broken} c: Systems! {send value/no value} d: FDIR! {display in tol/out-of-tol/no resp} a: Information display!{console} Displayproblem frame

  7. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Problem frames (cont.) • Problemdiagram 2/2: Information retrieval FDIR Storage System a c FDIR Retrieve information b d Crew/ Ground Control c:FDIR! {query} FDIR SS! {return data} a: FDIR SS!{status data} b:Crew!{search} FDIR!{display} d: Crew!{search} Commandedbehaviourproblem frame

  8. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Problemframes (cont.) • Conclusion:

  9. 2. Functionalrequirements Use-case & sequencesdiagrams Problem understanding Functional requirements (use-case model) Non-functional requirements Usability analysis & design

  10. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Use case diagram

  11. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Sequencediagrams • Safe response in case of hazardous conditions :

  12. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Sequencediagrams (cont.) • Start system, restart system & refresh system state :

  13. 3. Non-functionalrequirements Identified & improvisedqualityattributes Problem understanding Functional requirements (use-case model) Non-functional requirements Usability analysis & design

  14. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Identifiedattributes

  15. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Improvisedattributes

  16. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Improvisedattributes (cont.)

  17. 4. Usabilityanalysis & design Prototypes & usability scenarios discussions Problem understanding Functional requirements (use-case model) Non-functional requirements Usability analysis & design

  18. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design User interface design Screen 1 System List Screen 2 System Information Screen 3 Logs

  19. Problemunderstanding FunctionalRequirements Non-FunctionalRequirements UsabilityAnalysis & Design Usability scenarios discussions 24Views has to be consistent from one to another 25Modification in one screen affect the others 15Concurrent activities 16 Navigation within a single view 26Displaying in different views & ways 03 Canceling actions 19 Display expected duration of any action

  20. conclusion

  21. Project 1 Problemunderstanding & UI design FDIRSpacecraft fault protection system Euro Team Alauzet Pierre, Ahvenniemi Mikko, Colin Julien, Starck Benoit CS554 - Design for Software & Systems

  22. references • [Eas98] Steve Easterbrook, and et al., Experiences Using Lightweight Formal Methods for Requirements Modeling” IEEE Transactions on Software Engineering, Vol. 24, No. 1, January 1998. • [Jac05] Michael Jackson, Problem frames and software engineering, Information and Software Technology, Special Issue: 1st Int Workshop on Advances and Applications of Problem Frames, K. Cox, et al. eds, Vol. 47 No. 14, pp. 903-912, Nov. 2005. • http://www.bredemeyer.com/pdf_files/NonFunctReq.PDF,about non-function requirements

More Related