Analysis and Modeling of Software Systems

Analysis and Modeling of Software Systems

1. Unified Process Phases

   • Inception
     • Establish the case for the viability of the proposed system.
     • Risks
       • Vulnerabilities of any of the stages
       • Technical
       • Wrong Requirement
       • Wrong Architecture
   • Elaboration
     • Establish the ability to build the new system given the constraints that the development project faces.
   • Construction
     • Build a system capable of operating successfully in beta customer environments.
   • Transition
     • Roll out the fully functional system to customers.
     • Release “Beta”
       • A pre-release of software that is given out to a large group of users to try under real conditions. Beta versions have gone through alpha testing

2. Workflows

   • Requerimients
     • Building the use case model, which captures the functional requirements of the system being defined
   • Analysis
     • Building the analysis model, which helps the developers refine and structure the functional requirements captured within the use case model
   • Design
     • Building the design model, which describes the physical realizations of the use cases from the use case model, and also the contents of the analysis model
   • Implementation
     • Building the implementation model, which describes how the elements of the design model are packaged into software components, such as source code files
   • Testing
     • Building the test model, which describes how integration and system tests will exercise executable components from the implementation model
   • Flow deliverables
     • Domain Model
       • Formal representation of a knowledge domain with concepts, roles, datatypes, individuals, and rules, typically grounded in a description logic.
     • Business Case
       • Includes business context, success criteria (revenue projection, market recognition, and so on), and financial forecast.
     • Requirements
       • Is the process of determining user expectations for a new or modified product
         • Miller's Law: The average person can only keep 7 (plus or minus 2) items in their working memory.
     • Architecture
       • The shared understanding that the expert developers have of the system design, fundamental organization of a system
     • Risks
     • Management Plan
       • Objectives of the proposed project, including clearly defined responsibilities, timelines, and milestones
     • Business Model
       • Describes the rationale of how an organization creates, delivers, and captures value

3. José Ernesto García Torales A01365919

Bilder und Dateien der Mindmap