1. Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
Sanchit Agarwal
Nikita Pandey

2. Outline Process Centric vs Product Centric Project Lifecycle
Root Causes
Suggested solutions
Recommended solution
Test Process Map

3. Product-Centric vs Process-Centric
Product centric : Very small projects need product centric approach.
Process centric: Large and long term projects need process centric approach, where requirements are not stable and it keeps on changing and a well defined hierarchy exist in the company

4. Stages in Project Lifecycle
Conceptualization
Problem is analyzed well along with discussion of trade-off
Result : Business Case and Vision Document
Requirements Elicitation and Analysis
Document what qualities the application must exhibit
Result : Requirements Specification Document
Software Architecture and Design
Structure the application at different levels of detail
Result : Detailed Design Document

5. Stages in Project Lifecycle (Cont.)
Coding
Subject to company coding standards
Result : Implemented collection of modules
Integration and System Testing
Test collections of modules as they are integrated
At final stage, system testing is done on running application
Delivery, Deployment and User Training
Post-development activities
Maintenance
Correction of errors, software enhancement and perfection
Retirement

6. Root Causes Visibility Problem: No tracking of project growth
Module testing was not carried out at the coding phase. This burdened the system testing.
Planning Problem : Team size was doubled at the later stage of the project, which further delayed the project.
CRM didn’t negotiate over the deadlines even when the situation demanded
While ignoring 80% of the test processes, no analysis was made as to which necessary processes must be followed, and which one should be skipped.

7. Separate Test Teams Pros: Cons:
They will start from requirement stage to design a series of a test cases that have a high likelihood of finding errors
Module testing must be followed
Pros:
Test cases will be more complete & hence it will uncover almost all the errors
Saves time , since test teams will work in parallel with the coding team
Cons:
Cost of the project goes up

8. Automated Testing Tools
Load Testing Tool
Determining the points at which the capacity and performance of the system become degraded to the situation that hardware or software upgrades would be required eg. MS Web Application Stress Tool, Apache Bench
Performance Testing Tool
providing assurance that the performance of the system will be adequate in various situations eg. NTime

9. Pros And Cons Pros : Cons :
Fast: Automated Tools run tests significantly faster than human users.
Better Quality Software: Because you can run more tests in less time with fewer resources
Cons :
If the right test tools are not selected, the purpose of test automation will fail.
Learning automated tools takes time

10. Formal Technical Review
Review other people’s work
Used to detect defects in requirements, design, code and test cases
Pros :
Find defects earlier than testing does. This saves time and increases the development speed.
Developers share knowledge with each other. This enhances their rapid development capability.
Cons :
Since it is a manual process it may take a lot of time

11. Tracking of Project Growth
Tracking can be done in different ways :
Milestones can be chalked out initially, and later check whether these milestones are accomplished by the scheduled date.
Project status meetings can be conducted at regular intervals
Pros:
We’ll have a visibility of the project, so we won’t be crossing the deadline

12. Recommended Solution Track project growth
New testing team should be formed which will perform module testing
Use automated test tools
Follow technical review

13. Test Map Requirement Analysis (exercise input /output domain)
Design Analysis
(exercise internal program logic)
Test Planning
Test Development
Test Execution
If bugs found
Report and proceed to
next phase
yes No
Report and Fix Bugs

14. Thank you !

15. Process
A framework for the tasks that is required to build high quality software.

16. Pros
Following organizational values/method saves time, effort and prevents rework
Ensures consistency in work quality and schedules
Predetermined style of working makes it easy for a newcomer to fall into the groove
Debugging becomes easier to do
Version control of all design documents/files

17. Pros (contd…)
If someone left the company its part could be easily be given to some other person.
Keep track of how work is done, helpful if wants to make changes or additions.
Work could be easily divided and integrated.
Reliability, Visibility and maintainability, clarity, extensibility are easy to attain.

18. Cons If we work out the Schedule properly, then innovation is possible
Sometimes chances to optimize the process are missed due to rigidity
In smaller projects, sometimes better to follow a continuous consult- review- incorporate process (iterative development)
More formality means less dynamism
More man power and money is needed
Employee motivation and commitment levels less as they don’t get full credit for work, they are just part of the system, or that they don’t get 'real' work
If we want to have quick delivery then following a process can take more time.