Bài Giảng Phân tích thiết kế hướng đối tượng (phần 2)

InceptionLecture 2Hoa Sen University1.Agenda      Recap Inception overview Evolutionary Requirements Use cases Other requirements Assignment 1 instructionHoa Sen University2.What we learned last week Difference
Nội dung trích xuất từ tài liệu:
Bài Giảng Phân tích thiết kế hướng đối tượng (phần 2)Inception Lecture 2Hoa Sen University 1 Agenda Recap Inception overview Evolutionary Requirements Use cases Other requirements Assignment 1 instruction Hoa Sen University 2 What we learned last week Difference between analysis and design Different focuses of functional decomposition and object-oriented approach Benefit of OO approach UML Iterative development Agile modelling Hoa Sen University 3 Inception Questions What is the vision and the business case for this project? Feasible? Buy and/or build? Rough estimate of cost: $10K, $100K, $1M,… Should we proceed or stop? Hoa Sen University 4 Goals of Inception “…to do just enough investigation to form a rational, justifiable opinion of the overall purpose and feasibility of the potential new system.” Envision the product scope, vision and business case Do the stakeholders have basic agreement on the vision of the project? Is it worth investigating seriously? Hoa Sen University 5 Artefacts in InceptionArtefacts CommentsVision and Business Describe the high-level goals and constraints, the business case, andCase provides an executive summaryUse-Case Model Describes the functional requirements. During inception, the names of most use cases will be identified, and perhaps 10% of the use cases will be analysed in detailSupplementary Other requirementsspecificationGlossary Key domain terminology, and data dictionaryRisk List & Risk Describes the risks (business, technical, resource, schedule) and ideas forManagement plan their mitigation or responsePrototypes and proof-of- To clarify the vision, and validate technical ideasconceptsIteration Plan Describes what to do in the first elaboration iterationPhase Plan & Software Low-precision guess for elaboration phase duration and effort. Tools,Development plan people, education, and other resourcesDevelopment Case A description of the customized UP steps and artefacts for this project. Hoa Sen University 6 It is not an inception if It takes more than a few weeks You attempt to define most requirements Estimates are expected to be reliable You define a concrete architecture No business case or vision document Too little or too much use case modelling Hoa Sen University 7Hoa Sen University 8 Understanding Requirements “Capabilities and conditions to which the system and project must conform” [Jacobson et al., 1999] Challenges: {find, communicate, record, manage} the requirements Requirements always change, so effective management is critical Hoa Sen University 9 Evolutionary vs. Waterfall requirements UP embraces change in requirements as a fundamental driver on projects Start production-quality programming and testing long before most of the requirements have been analysed or specified. Hoa Sen University 10 The FURPS+ Model Functional – features, capabilities, security Usability – human factors, help, documentation Reliability – failure frequency, recoverability Performance – response times, throughput, accuracy, availability, resource utilization Supportability – adaptability, maintainability, internationalization, configurability Hoa Sen University 11 The FURPS+ Model Implementation – resource limitations, languages/tools, hardware Interface – with legacy systems Operations – sysop management Packaging – delivery, installation Legal – licensing, etc. Use FURPS+ as a global checklist when identifying requirements for a system you are designing Hoa Sen University 12 Other Terminology Quality Attributes, or “-ilities” – Usability, reliability, supportability, performance (non-functional) Functional vs. Non-Functional – Behavioural features vs. everything else The quality attributes have a strong influence on the architecture of a system Hoa Sen University 13 Document Requirements Primarily, in the use case model – functional requirements Also, Supplementary Specifications – other requirements Glossary – noteworthy terms Vision – high-level requirements Business Rules – Requirements or policies that transcend one software ...