1characteristics of a good process
TRANSCRIPT
![Page 1: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/1.jpg)
Characteristics of a good process
• Process should be precisely defined.• The step must be predictable.• Predictable process should be under statistical
control.• Process should support testing and
maintainability.
![Page 2: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/2.jpg)
SDLC(Software development life cycle)
• Problem definition• Feasibility study• Analysis• System Design• Detailed design• Implementation• Maintenance
![Page 3: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/3.jpg)
Problem Definition
This phase establish problem and define problem
To answer:• What is the problem• Who faced the problem• Where in the organization
![Page 4: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/4.jpg)
Idea:• Meet user and management and obtain a
solution to their problem• If problem exist it need to be solved and
becomes a project• After this funds and resources are applied
![Page 5: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/5.jpg)
Problem definition Document
• Project Title• Problem statement• Objective of project• Possible solutions• Project Scope• Indicate time and cost for feasibility step
![Page 6: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/6.jpg)
Feasibility study
Types of feasibility:-1. Economical2. Technical3. Operational
![Page 7: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/7.jpg)
Feasibility study report
1. Introduction-state problem-user environment-kind of solution you are preparing-kinds of constraints on the
project( cost, time, etc…)2. Recommendations3. Alternatives—for final approach
![Page 8: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/8.jpg)
4. System description5. Cost benefit analysis6. Evaluation of technical risk7. Legal Ramification
![Page 9: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/9.jpg)
Waterfall Model
• Produces many intermediate deliverable usually documents- which acts as a baseline
• Important for quality assurance and project management
• Widely used when requirement are well understood
![Page 10: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/10.jpg)
System Engineering
Coding
Design
Analysis and Gathering
Testing
Deployment
Maintenance
![Page 11: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/11.jpg)
System engineering
• Understand overall context of problem• Identify the responsibilities to be make
![Page 12: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/12.jpg)
Analysis
• Problem domain is analyzed in more detail.Understand:-1. What kind of information is involved2. What kind of data is involved3. What functions need to be performed4. What are the performance and interfacing
requirements5. Purpose is to clearly defined the requirement
which are to be met
![Page 13: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/13.jpg)
6. Also carry out project planning as part of same step
Purpose is to identify:1. What are the different steps2. What are different deliverables3. What would be the timeframe4. What would be the resources allocated
![Page 14: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/14.jpg)
Design
Requirements are translated to1. software architecture2. Prepare database design
![Page 15: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/15.jpg)
Design is divided into two parts:
1. High level design2. Low level design or detailed design
![Page 16: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/16.jpg)
Coding
![Page 17: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/17.jpg)
Testing
1. Unit testing2. Integration testing3. System testing
![Page 18: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/18.jpg)
Deployment of software
• Implemented and Released• User will take control and start using software
![Page 19: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/19.jpg)
Ongoing Maintenance
• If errors encountered necessary changes need to be made
• Performance requirement need to review.
![Page 20: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/20.jpg)
Deliverables in waterfall model
1. Project Plan and feasibility report2. SRS(Software requirement specification) or
requirement document3. Design document:
- System design document- Detailed design document
4. Test Plans and Test Reports
![Page 21: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/21.jpg)
5. Source code6.Software manuals (user manual, Installation
Manual)7. Review Reports (catalog how development
went through)
![Page 22: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/22.jpg)
When to use the Waterfall Model
• Requirements are very well known• Product definition is stable• Technology is understood• New version of an existing product
![Page 23: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/23.jpg)
Waterfall Strengths
• Easy to understand, easy to use• Provides structure to inexperienced staff• Milestones are well understood• Sets requirements stability• Good for management control (plan, staff, track)• Works well when quality is more important than cost
or schedule
![Page 24: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/24.jpg)
Shortcomings in waterfall model
1. Requirement may not be completely known2. Requirement changes with time3. Heavy Documentation
![Page 25: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/25.jpg)
V-Shaped SDLC Model• A variant of the Waterfall
that emphasizes the verification and validation of the product.
• Testing of the product is planned in parallel with a corresponding phase of development
![Page 26: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/26.jpg)
V-Shaped Steps• Project and Requirements Planning –
allocate resources
• Product Requirements and Specification Analysis – complete specification of the software system
• Architecture or High-Level Design – defines how software functions fulfill the design
• Detailed Design – develop algorithms for each architectural component
• Production, operation and maintenance – provide for enhancement and corrections
• System and acceptance testing – check the entire software system in its environment
• Integration and Testing – check that modules interconnect correctly
• Unit testing – check that each module acts as expected
• Coding – transform algorithms into software
![Page 27: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/27.jpg)
V-Shaped Strengths
• Emphasize planning for verification and validation of the product in early stages of product development
• Each deliverable must be testable• Project management can track progress by
milestones• Easy to use
![Page 28: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/28.jpg)
V-Shaped Weaknesses
• Does not easily handle concurrent events• Does not handle iterations or phases• Does not easily handle dynamic changes in
requirements• Does not contain risk analysis activities
![Page 29: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/29.jpg)
When to use the V-Shaped Model
• Excellent choice for systems requiring high reliability – hospital patient control applications
• All requirements are known up-front• When it can be modified to handle changing
requirements beyond analysis phase • Solution and technology are known
![Page 30: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/30.jpg)
Structured Evolutionary Prototyping Model
• Developers build a prototype during the requirements phase
• Prototype is evaluated by end users• Users give corrective feedback • Developers further refine the prototype• When the user is satisfied, the prototype code
is brought up to the standards needed for a final product.
![Page 31: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/31.jpg)
Evolutionary Delivery
Rapid Development, Taming Wild Software Schedules, by Steven McConnell, Press 1996
![Page 32: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/32.jpg)
Structured Evolutionary Prototyping Steps
• A preliminary project plan is developed• An partial high-level paper model is created• The model is source for a partial requirements specification• A prototype is built with basic and critical attributes• The designer builds
– the database – user interface – algorithmic functions
• The designer demonstrates the prototype, the user evaluates for problems and suggests improvements.
• This loop continues until the user is satisfied
![Page 33: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/33.jpg)
When to useStructured Evolutionary Prototyping
• Requirements are unstable or have to be clarified • As the requirements clarification stage of a waterfall
model• Develop user interfaces• Short-lived demonstrations • New, original development
![Page 34: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/34.jpg)
Limitations
1. Customer may want prototype itself (not maintainable, bad performance) 2. Developers may continue with
implementation choices(bad quality performance)
3. Good tools are required for quick development
4. May increase project cost
![Page 35: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/35.jpg)
Incremental SDLC Model• Construct a partial
implementation of a total system • Then slowly add increased
functionality• The incremental model prioritizes
requirements of the system and then implements them in groups.
• Each subsequent release of the system adds function to the previous release, until all designed functionality has been implemented.
![Page 36: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/36.jpg)
Incremental Model Strengths
• Develop high-risk or major functions first• Each release delivers an operational product • Customer can respond to each build• Uses “divide and conquer” breakdown of tasks• Lowers initial delivery cost • Initial product delivery is faster• Customers get important functionality early• Risk of changing requirements is reduced
![Page 37: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/37.jpg)
Incremental Model Weaknesses
• Requires good planning and design• Requires early definition of a complete and
fully functional system to allow for the definition of increments
• Well-defined module interfaces are required (some will be developed long before others)
• Total cost of the complete system is not lower
![Page 38: 1Characteristics of a Good Process](https://reader035.vdocuments.mx/reader035/viewer/2022070523/577ccd041a28ab9e788b477d/html5/thumbnails/38.jpg)
When to use the Incremental Model • Risk, funding, schedule, program complexity, or need
for early realization of benefits.• Most of the requirements are known up-front but are
expected to evolve over time• A need to get basic functionality to the market early• On projects which have lengthy development
schedules• On a project with new technology