Software Engineering, CPSC-4360-01, CPSC-5360-01, Lecture 2

of 54 /54
06/17/22 CPSC-4360-01, CPSC-5360-01, Lecture 2 1 Software Engineering, CPSC-4360-01, CPSC-5360- 01, Lecture 2

Embed Size (px)

description

Software Engineering, CPSC-4360-01, CPSC-5360-01, Lecture 2. Overview of the Last Lecture. Overview of Software Engineering SE definitions Quality of Good Software Overview of Software Process Activities and associated stages Overview of Software Engineering Method Structured Analysis - PowerPoint PPT Presentation

Transcript of Software Engineering, CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Software Engineering, CPSC-4360-01, CPSC-5360-01,Lecture 2

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Overview of the Last LectureOverview of Software EngineeringSE definitionsQuality of Good SoftwareOverview of Software ProcessActivities and associated stagesOverview of Software Engineering MethodStructured AnalysisObject-Oriented Method

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Overview of This LectureSoftware Development ModelsWaterfall ModelEvolutionary ModelsIncremental ModelSpiral ModelUnified ProcessOverview of UMLHistory4 + 1 View modelsUsing UML in UP

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Software Development ModelsHigh level, abstract representation of software development (software process):Specification.Development.Validation.Evolution.Theoretical framework that is usually extended and adapted in real world application.Two Generic Models:Waterfall Model.Evolutionary Model.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall ModelThe earliest software development model (Royce, 1970).

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall ModelDefined a number of phases, e.g., requirement phase, design phase, etc.The phases correspond to the four stages of the fundamental software process activities (lecture 1).Assumption behind the model:a phase takes place in sequence to another.each activity is completed before the next starts.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall ModelIn theory:Each phase produces documents that are:Verified and validated.Assumed to be complete.Each phase depends on the documents of the previous stage to proceed it has to wait for the completion of previous stage.In practice:The phases overlap and feedback to each other (see the feedback arrow in the diagram).

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall Model: AdvantagesTangible products (the various documents) at the end of every phases good to measure progress.Intuitive, sensible and general purpose:Emphasize planning before action.Recommend a top-down perspective. See the big picture before zooming down.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall Model: ProblemsSpecification is frozen early, because:It is costly and time consuming.Later stages can be carried out.Cannot adapt to changing or incorrect specification:Ignore or code around.Does not meet user requirement.Testing at the very end of development:Work or die situation.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Waterfall Model: ObservationsProcess stages can be iterative.Flexibility in coping with changing specification.Early and frequent validation of software system.The later models are designed in response to these observations.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Evolutionary ModelEvolves an initial implementation with user feedback multiple versions until the final version.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Evolutionary ModelTwo fundamental types:Exploratory Development: Explores the requirement and delivers a final system.Starts with something that is understood and evolves by adding new features proposed by customers.Throwaway prototyping: Understands the requirement and develop a better requirement definition.Experimenting with poorly understood requirement.Usually develops User Interface (UI) with minor or no functionality.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Evolutionary Model: AdvantagesCustomer involvement in the process:More likely to meet the user requirement.Early and frequent testing:More likely to identify problems.Lower risk.Suitable for small to medium sized system.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Evolutionary Model: ProblemsThe process is intangible:No regular, well-defined deliverables.The process is unpredictable:Hard to manage, e.g., scheduling, workforce allocation, etc.Systems are poorly structured:Continual, unpredictable change tends to corrupt the software structure.Can cause major problems during software evolution.Systems may not even converge to a final version.No strategy to gauge or solve this problem.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Incremental ModelCombine the advantages of Waterfall and Evolutionary Model.Final System

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Incremental ModelEach increment is a mini-waterfall.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Incremental ModelPrioritizes the services to be provided by the system.Maps these requirements to Increment based on priority.Freezes requirement for the current Increment.Requirements for the later increments can evolve concurrently.Each Increment release is a working system:Allows user to experiment.Can be put into service right away.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Incremental Model: AdvantagesEarly utilization: the 1st increment satisfies the most critical requirement.Early increments can serves as prototypes.Lower risk of overall project failure.Most crucial and basic services are implemented first receives multiple testing throughout development.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Incremental Model: ProblemsHard to map requirement into small increments (< 20,000 lines of code).Hard to define the basic services that are shared by all subsequent increments.Popular variant:AGILE method:eXtreme Programming (XP)Not covered here.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Spiral ModelFormalize the Evolutionary Model and avoid the management shortcomings.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Spiral ModelProcess is represented as a spiral rather than as a sequence of activities with backtracking.Each loop = One Iteration = A process phase.Each Loop passes through 4 quadrants (90):Objective Setting.Risk Assessment and Reduction.Development and Validation.Planning.As loops move away from center Time and Cost increase.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Spiral ModelRisk Driven:Explicitly identify risks for each iteration.Address the highest perceived risk.Does not prescribe a fix process:Project Manager chooses the appropriate activity for each iteration base on progress and perceived risk.Flexible: May resemble other process model depends on needs.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Unified ProcessState of the art process, by learning from the history of previous software development processes.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Unified ProcessIntegrating two seemingly contradicting insights:Definitive activities and deliverables as in the Waterfall Model.Iterative and incremental processes.A project is split into several phases:Each phase is split into several iterations.Each iteration consists of the traditional process activities, known as workflow.Each workflow places different emphasis on the activities depending on the current iteration.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Unified Process: 4 PhasesInception: Plan the project.Evaluate risk.Elaboration:Understand problem domain.Design system architecture.Plan development.Construction:Design, programming and test.Transition:Moving system from developer to user environment.Acceptance testing, release of full system.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Other Process ModelsFormal System Development:Transforms a mathematical based specification through different representation executable program.Program correctness is easy to demonstrate, as the transformations preserve the correctness.Reuse-Oriented Development:Concentrates on integrating new system with existing components/systems.Growing rapidly as development cost increase.Aspect-Oriented Development.Agent-Oriented Software Development.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Unified Modeling Language (UML)A visual language to Visualize, construct, document software system.Similar to all other languages, UML has:Grammar: Rules to follow when drawing diagrams.Semantics: The meaning behind each diagram.Used with the Object-Oriented Method.Separates the language from the software process can be used with other software development model.Currently, this is an industry standard.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*What UML is NOTNot a programming language.Not executable.Exist tools to translate into code (skeleton), but the programmer still need to do the bulk of work.Not a software modeling tool.There are tools that implement the UML standard, e.g., ArgoUML, Visual Paradigm, RationalRose.Not a SE method or software development process.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML: Brief HistoryOO Modeling approach with different strengths and weaknesses grows rapidly. In 1995, There were more than 50 named techniques in the industry.The Object Management Group (OMG) calls for a common modeling approach.Rumbaugh, Booch, and Jacobson (The three amigos) with input from others, formalized the UML standard (UML 1.1) in 1997. Revised in 2003 (UML 1.5): Currently most widely used.Reorganized in 2005 (UML 2.0): A new standard.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML: 4 + 1 View ModelsA system can be viewed in different ways, usually depends on the role of the viewer.UML supports this by providing the 4 + 1 View Models [Kruchten, 1995]:System

    Design ViewImplementation ViewDeployment ViewProcess ViewUse Case View

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Use Case ViewAudience:System Analyst, End Users and Testers.Usage:Describes the systems external behaviour.Defines the requirements of the system, so it constraints all the other views.Has the central role in driving the development process.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Example of Use CaseElevator SystemUse case 1: Call Elevator is this possible written story:Basic course of events: If the userOutside wants to call lift to go up/down, then he/she presses UpButton/DownButton;Exception 1: If the lift is at the ground floor, then there is no DownButton;Exception 2: If the lift is at the top floor, then there is no UpButton;Use case 2: Move From Inside is this written story:The userFromInside can select a floor number (from 1 to the number of floors of the building), or can press Open, Close.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Design ViewAudience:System Analyst and Programmers.Usage:Describes the logical structures that support the functional requirements expressed in the use case view.Consists of definitions of program components (classes, data), their behaviour and interactions.Useful as basis for coding.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Implementation ViewAudience:System Engineer and Tester.Usage:Describes the physical components out of which the system is to be constructed:executable files, libraries of code,databases.Useful for configuration management and system integration.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Process ViewAudience:System Analyst, Programmer and Tester.Usage:Non-Functional requirements.Defines concurrency within the system.Relatively undeveloped.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Deployment ViewAudience:System Integrator (setup the system at client side).Usage:Non-Functional.Describes physical components that are deployed in the physical environment:Network of computers, connection protocol.Computer specification.Relatively Undeveloped.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML TerminologyModel:Refers to the information in a single view, e.g., Use Case Model. ORRefers to all the information about the system, i.e., System Model.Model element:Independent graphical notation element, e.g., a box, an arrow, etc, that has a well defined meaning.Diagram:Graphical presentation of a collection of model elements.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML Diagrams by ViewsUse case diagram (use case view)Object diagram (use case and design views)Sequence diagram (use case and design views)Collaboration diagram (use case and design views)Class diagram (design view)Statechart diagram (design and process views)Activity diagram (design and process views)Component diagram (implementation view)Deployment diagram (deployment view)

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML Diagrams by Characteristic Software system exhibits two characteristics:Static: Logical Structure, e.g., relationship between classes, attributes of a class, etc.Dynamic: Behavior of the system, e.g., how to respond to a certain event, how to initiate an action, etc.In addition, knowledge about setting up and running the system: Implementation.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML Diagrams by CharacteristicStatic:Use case diagram Class diagramDynamic:Object diagram State diagram Activity diagram Sequence diagram Collaboration diagramImplementation:Component diagramDeployment diagram

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Design Model and CodeModels present an abstract view of system. Implementation adds enough detail to make these models executable.

    UML modelObject structuresUMLJavaAbstract view ofAbstract view ofspecifiesspecifiesCompile timeRun time

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UML ModelsBoth documentation (UML model) and Source code can be described as compile-time artifacts.Object structures: Programmers in object-oriented languages (e.g., Java, C++) tend to use abstract models of program execution which talk in terms of objects being created and destroyed as a program runs.Executing program: describes the effect the program has on computers processor and memory when the program is running.The upper and below parts refer to design and programming.The left and right parts refer to compile-time and run-time.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Unified Process and UMLUP is Use Case Driven:A systematic utilization of Use Case.UML diagrams are used in the Requirement, Analysis and Design activities in the UP workflow.Because of their history, there is a close fit between UML and the UP.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UP: Requirement and AnalysisUP starts with use cases describing how users interact with the system:A domain model records facts about real world entities.UML use case and class diagrams document these.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UP: Analysis and DesignAnalysis and Design usually overlap in UP as the same diagrams are used.Proceed by Realization and Refinement.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UP: Realization and RefinementUse case realizations indicate how the functionality will be supported by the system.Documented in UML interaction diagrams, e.g., Sequence Diagram, Collaboration Diagram.This causes the domain model to be refined into a more implementation-oriented class diagram.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*UP: Specifying BehaviorUML provides State Chart to document the behavior of classes.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Summary (1)Waterfall Process Model:Development activities in a linear fashion.Requirements to freeze very early in development.Testing very late in the process.Evolutionary Process Model in response to iterative nature of development:Use of prototyping.Requirements evolve with users feedback.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Summary (2)Incremental Process Model in response to incremental nature of development:Delivery in increments.Allows prioritizing risks in development.Allows different process models for different increments.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Summary (3)Spiral Model:Addresses incremental and iterative nature of development.Allows risk evaluation at every phase.Expensive process.Allows use of multiple process models.Unified Process:Incorporates best industry practices.Extensive use of UML models.Allows iteration of workflows.

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*SummarySoftware Development ModelsWaterfall ModelEvolutionary ModelsIncremental ModelSpiral ModelUnified ProcessOverview of UMLHistory4 + 1 View modelsUsing UML in UP

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Reading Suggestions[Wadhwa, Andrei, Soo; 2007], Chapter 2[Sommerville; 2008], Chapters 1 and 4[Priestley; 2004], Chapter 3

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Coming up nextUse Case Modeling, Domain Modeling:[Wadhwa, Andrei, Soo; 2007], Chapters 2 and 3[Priestley; 2004], Chapter 4

    CPSC-4360-01, CPSC-5360-01, Lecture 2

  • *CPSC-4360-01, CPSC-5360-01, Lecture 2*Thank you for your attention!

    Questions?

    CPSC-4360-01, CPSC-5360-01, Lecture 2