1. University of Southern California Center for Systems and Software Engineering 577 process CSCI 577a Software Engineering I Supannika Koolmanojwong Mobasser September 4, 2015

2. University of Southern California Center for Systems and Software Engineering Outline Processes –Architected Agile / NDI-intensive –Resilient Agile Roles and Responsibilities (c) 2007-2015 USC CSSE2

3. University of Southern California Center for Systems and Software Engineering Timeline – Architected Agile (c) 2007-2015 USC CSSE3 FCR ARB Team formation and project selection DCR ARB Win Win Negotiation Lead by shaper / requirements engineer Prototype 1 Operational Concepts Prototype 2 Prototype 3 Prototype 4 Prototype 5 Sw architect Life Cycle Planner Feasibility Analyst Project Manager Quality Focal Point

4. University of Southern California Center for Systems and Software Engineering Timeline – Resilient Agile (c) 2007-2015 USC CSSE4 FCR ARB Team formation and project selection DCR ARB Win Win Negotiation Lead by shaper / requirements engineer Benefit Chain, Program Model Business case Analysis Project Manager Quality Focal Point Resource Planning Cost Estimation Storyboard UC Scenarios, Robustness diagram Sequence, class diagrams functional prototype Req, UC diagram, Traceability between Req and UC D, Domain Model

5. University of Southern California Center for Systems and Software Engineering Common Deliverables (c) 2007-2015 USC CSSE5 ArtifactsSubmission timelines Quality Management PlanFCR ARB PersonaFCR ARB Technical DebtFCR ARB; DCR ARB MetricDCR ARB RisksBi-weekly - Done by QFP DefectsBi-weekly - Done by QFP Progress ReportBi-weekly - Done by Project manager Project planBi-weekly - Done by Project manager Acceptance TestDone individually as homework

6. University of Southern California Center for Systems and Software Engineering Differences in Deliverables (c) 2007-2015 USC CSSE6 DifferencesArchitected AgileResilient Agile Responsibilities Role-based responsibilities - students have their own primary and secondary responsibilities Use case - based responsibilities with shared artifacts : The whole team shares common artifacts. Then each one developed their own use case package (UC, Req, scenarios, diagrams) Role OCD, Req, LCP, FED, Pro, Arch, QFP, PM System integrator, developers, QFP, PM Development style Incremental & overlapping artifact development Concurrent use case-based development Artifacts Win conditions Requirements and use case scenarios Risk-based prototypes with navigation flow Story boards, functional prototypes UC, Class, Seq, DB Domain Model; UC, Rob, Seq, Class Diagram, DB ImplementationDeveloper and Test teamsCode your own UC

7. University of Southern California Center for Systems and Software Engineering Tailored Deliverables (c) 2007-2015 USC CSSE7 Architected AgileResilient Agile Operational Concept Description Benefit Chain Diagram Program Model Life Cycle Plan Resources allocation Cost Estimation Feasibililty Evidence DescriptionBusiness Case Analysis

8. University of Southern California Center for Systems and Software Engineering Deliverables (c) 2007-2015 USC CSSE8

9. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE9

10. University of Southern California Center for Systems and Software Engineering Roles (c) 2007-2015 USC CSSE10

11. University of Southern California Center for Systems and Software Engineering 577a roles Architected Agile Operational Concept Engineer Prototyper Requirements Engineer UML modeler Software architect Life cycle planner Feasibility analyst Quality focal point/ IIV&V Project Manager Resilient Agile Developer System Integrator Quality Focal Point Project Manager (c) 2007-2015 USC CSSE11

12. University of Southern California Center for Systems and Software Engineering Operational Concept Engineer (c) 2007-2015 USC CSSE12

13. University of Southern California Center for Systems and Software Engineering Prototyper (c) 2007-2015 USC CSSE13

14. University of Southern California Center for Systems and Software Engineering Requirements Engineer (c) 2007-2015 USC CSSE14

15. University of Southern California Center for Systems and Software Engineering UML Modeler (c) 2007-2015 USC CSSE15

16. University of Southern California Center for Systems and Software Engineering Software Architect (c) 2007-2015 USC CSSE16

17. University of Southern California Center for Systems and Software Engineering Life Cycle Planner (c) 2007-2015 USC CSSE17

18. University of Southern California Center for Systems and Software Engineering Feasibility Analyst (c) 2007-2015 USC CSSE18

19. University of Southern California Center for Systems and Software Engineering Quality Focal Point Activities –Assure quality of the project Artifacts –Bi-weekly risk report –Bi-weekly defect report (c) 2007-2015 USC CSSE19