1. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Engineering Goals: Develop quality software What is quality of a software

2. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Engineering Goals: Develop quality software 1.Define Quality: depends on Perspective 1.User’s View (Unix vs Windows vs Mac) 2.Manufacture's View (up to the specifications) 3.Designer’s View (UI and Architecture) Outcome: User’s External View, Developer’s Internal View

3. By Manish Shrotriya CSE300 2014MS From: Software engineering theory and practice by Pfleeger, Atlee

4. By Manish Shrotriya CSE300 2014MS Correctness Reliability Efficiency Usability Maintainability Reusability Traceability Consistency Access control Execution Eff. Simplicity Operability Reusability Training Modularity Generality

5. By Manish Shrotriya CSE300 2014MS From: Software engineering theory and practice by Pfleeger, Atlee

6. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Engineering Goals: Develop quality software 2.Establish Development Process to ensure Quality 1.Waterfall Model 2.Spiral model 3.Agile Question: How to manage your project to effectively follow a process. How to measure your process

7. By Manish Shrotriya CSE300 2014MS

8. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Engineering Goals: Develop quality software Question: How to manage your project to effectively follow a process? How to measure your process? Answers: CMM, Capability Maturity Model By Carnegie Mellon University

9. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Ex: Waterfall Model but poor process Two guys talk to Customer, note requirements pass them to 3 developers, One creates design working overnight, rest 2 would code and test. Product is ready to deliver. Risks:

10. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Ex: Waterfall Model but poor process Two guys talk to Customer, note requirements, pass them to 3 developers, One creates design working overnight, rest 2 would code and test. Product is ready to deliver. Solution: planning, configuration management, requirements management, quality assurance.

11. By Manish Shrotriya CSE300 2014MS CMMI Maturity Model

12. By Manish Shrotriya CSE300 2014MS

13. By Manish Shrotriya CSE300 2014MS Capability Maturity Model What is Process Maturity Well defined Effective Repeatable Measured (our customer discussion) Analyzed Improved Our Projects. What do we have as processes?

14. By Manish Shrotriya CSE300 2014MS Identify Immaturity of Organization/Project Reactive not proactive (Crisis driven) Saved by Heroes Improper/unrealistic budget Quality/schedule Processes are ignored Processes are improvised No well defined quality structure

15. By Manish Shrotriya CSE300 2014MS What is Maturity of Organization and Project Work is done according to laid out plan Well defined roles and responsibility Coordination and communication Improvement of processes Processes are converted in practices How to identify what is missing or what to improve upon.

16. By Manish Shrotriya CSE300 2014MS Key Process Area (Level Based) Level 2 KPA Requirements Management (vendor and customer on same page) Project Planning (Schedule, Target/goals, Roles/Responsibility) Project Tracking & Oversight ( calculating progress, monitor efforts) Subcontract Management (select qualified vendors) Quality Assurance (testing results, enforcement) Software configuration Management

17. By Manish Shrotriya CSE300 2014MS Software Engineering vs Software Project Organization is plan driven and not crisis driven Next Step: Tolstoy’s principle, there is an infinite number of ways to fail, so improving by reacting to failures is a never-ending and fruitless struggle. Learning of one Project serves as the basis of organization wide policy. Ex: All project would use version control system for their code management.

18. By Manish Shrotriya CSE300 2014MS Key Process Area (Level Based) Level 3 KPA Organization Process Focus ( result is Process Assets) Organization Process Definition (ordered list of Assets ) Training Programs (Process training, Technology Training) Integrated Software Management (integrate Management and engineering in to one process) Intergroup Coordination (one department many Customers) Peer Reviews

19. By Manish Shrotriya CSE300 2014MS Key Process Area (Level Based) Level 4 KPA Quantitative Process Management (measure your process: budget, actual deliveries, customer satisfaction, staff satisfaction) Quality Management (Quality definition and measurement) Level 5 KPA Defect Prevention ( causal analysis) Technology Change Management (New tools, Google drive) Process Change Management (suggest and implement changes)

20. By Manish Shrotriya CSE300 2014MS Login & password Localhost:portLogin Page Home Page Settings Button App admin Page Select fixed UI app Click Add App admin Page. App added Click Home Home Page App visible Click Logout Logout ack Add first app usecase

21. By Manish Shrotriya CSE300 2014MS User Stories for Add App usecase SNActionResultEstimatesRemarks 1User enter localhost:port in browserLogin Page is shownLogin page mock up path 2User enters login, password on login page and click login Home page is shownHome page mock up path 3User enters login, password on login page and click login User is directed to registration page with login prefilled Registration page mock up path 4User enters localhost:post/C/A for registration Registration page is shown 5User fills registration and submitsHome page is shown