1. Identifying Needs and EstablishingIdentifying Needs and Establishing
RequirementsRequirements
ByBy –– Arsalan AmanArsalan Aman
How business process run live software with customHow business process run live software with custom
development & supportdevelopment & support

3. What are requirements?What are requirements?
 A requirement is a statement about an intended product that specifies what itA requirement is a statement about an intended product that specifies what it
should do or how it should perform.should do or how it should perform.
 Goal: To make as specific and clear as possible.Goal: To make as specific and clear as possible.
 Custom enhancement of Client either UI or Admin.Custom enhancement of Client either UI or Admin.
 System & process support changes frequently so Software should be updatedSystem & process support changes frequently so Software should be updated
accordingly.accordingly.

4. Why do we need Requirements?Why do we need Requirements?
 The requirements gathering process involves communication with top
management, managers, customers and sometimes end-users. After gathering
functional requirements for presentation, business logic and data layers the work
on the software project is passed on to software architects, who will be tasked
with software design.
 Meetings with managers, stake holders and users are held in order to determine
the requirements like;
• Who is going to use the system? How will they use the system? What should be
the design?
• What data should be input into the system?
• What data should be output by the system?
 These are general questions that get answered during a requirements gathering
phase. After requirement gathering these requirements are analyzed for their
validity and the possibility of incorporating the requirements in the system to be
development is also studied.

5. Design By Application Development
Team
 Communicate & then They Create Tickets issues wise or enhancementCommunicate & then They Create Tickets issues wise or enhancement
 Data requirements: Capture the type, volatility, size/amount, persistence, accuracyData requirements: Capture the type, volatility, size/amount, persistence, accuracy
and the amounts of the required data.and the amounts of the required data.
 This specification document is then used by the design and development teams as aThis specification document is then used by the design and development teams as a
master plan, comparing the ongoing progress of the project requirements to itsmaster plan, comparing the ongoing progress of the project requirements to its
actual development.actual development.
 Includes translation of the requirements specified in the SRS into a logical structureIncludes translation of the requirements specified in the SRS into a logical structure
that can be implemented in a programming language. The output of the designthat can be implemented in a programming language. The output of the design
phase is a design document that acts as an input for allphase is a design document that acts as an input for all
 the subsequent SDLC phases.the subsequent SDLC phases.

6. DevelopmentDevelopment
 This is where the solution begins to be developed. There may be iterationsThis is where the solution begins to be developed. There may be iterations
where the customer is asked to review works and provide feedback andwhere the customer is asked to review works and provide feedback and
approvals.approvals.
 Often during development, new issues may arise that are brought to lightOften during development, new issues may arise that are brought to light
that were unforeseen and may affect items within the solution that will needthat were unforeseen and may affect items within the solution that will need
to be addressed by proper consideration of all parties considered.to be addressed by proper consideration of all parties considered.

7. DevelopmentDevelopment
 Typically these situations are minor and usually benefit the solution byTypically these situations are minor and usually benefit the solution by
adding more functionality or flexibility than was originally planned.adding more functionality or flexibility than was originally planned.
 Unit testing is performed during development as it pertains to the nature ofUnit testing is performed during development as it pertains to the nature of
developing a unit or segment of the solution for functionality anddeveloping a unit or segment of the solution for functionality and
completeness. These same tests will be performed in the QA stage butcompleteness. These same tests will be performed in the QA stage but
Developers should test first themselves! Some time related issue fixed butDevelopers should test first themselves! Some time related issue fixed but
impact other system!!!!!impact other system!!!!!

8. Testing & Evaluation - Q.ATesting & Evaluation - Q.A
 The software quality assurance (SQA) plan is an outline of quality measuresThe software quality assurance (SQA) plan is an outline of quality measures
to ensure quality levels within a software development effort. The plan isto ensure quality levels within a software development effort. The plan is
used as a baseline to compare the actual levels of quality duringused as a baseline to compare the actual levels of quality during
development with the planned levels of quality. If the levels of quality aredevelopment with the planned levels of quality. If the levels of quality are
not within the planned quality levels, management will respondnot within the planned quality levels, management will respond
appropriately as documented within the plan.appropriately as documented within the plan.
Step 1.Step 1. Document the plan.Document the plan.
Step 2.Step 2. Obtain Management Acceptance.Obtain Management Acceptance.
Step 3.Step 3. Obtain Development Acceptance.Obtain Development Acceptance.
Step 4.Step 4. Plan for Implementation of SQA Plan.Plan for Implementation of SQA Plan.
Step 5.Step 5. Execute the Plan.Execute the Plan.

9. Deployment:
 After successful testing the product is delivered / deployed to the customer for
their use.))
 Re MeetingRe Meeting
We re-communicate to client and get feedback if its up to the mark so clientWe re-communicate to client and get feedback if its up to the mark so client
Happy or some time client change his requirement so we priorities it or doHappy or some time client change his requirement so we priorities it or do
enhancement accordingly.enhancement accordingly.

10. Application Development Team Application Development Team
ResponsibilityResponsibility
With the application tested and deployed into the client's workplace, the software
enters into the Maintenance Phase of the SDLC. Even with the best attention to
detail in the earlier phases, changes to the software may be necessary for a number
of reasons:
The client may not have tested the software thoroughly enough.
The client may think of ways to extend the software in ways that were unforeseen
before.
Software bugs are almost inevitable. If enough bugs accumulate, releasing an
improved version of the software may be in order.
The business rules that were put in place at design time may change, necessitating
changes in the software.

11. Business Process & Support Business Process & Support
ResponsibilityResponsibility
 Engage in daily responses of system process like, sales data sync, assignEngage in daily responses of system process like, sales data sync, assign
activities, changes roles & updates activities with multi reports andactivities, changes roles & updates activities with multi reports and
meetings for new enhancement.meetings for new enhancement.
 Follow up App Dev team on received requirements from Clients then matchFollow up App Dev team on received requirements from Clients then match
either its up to the mark or not!either its up to the mark or not!
 Manage metrics for support team areas along with Client.Manage metrics for support team areas along with Client.
 Analyses reports per client requirement andAnalyses reports per client requirement and
 reviews for direct reports.reviews for direct reports.

12. Business Process & SupportBusiness Process & Support
ResponsibilityResponsibility
 Deliver and drive new processes within Support organization and reworkDeliver and drive new processes within Support organization and rework
with App Dev team if enhancement needed.with App Dev team if enhancement needed.
 Contribute to call duties for escalation point company coverage andContribute to call duties for escalation point company coverage and
automate internal time taking daily/weekly tasks.automate internal time taking daily/weekly tasks.
 Communicate system updates with business partners and associates at allCommunicate system updates with business partners and associates at all
levels.levels.
 Create and manage documentation of team procedures and processes andCreate and manage documentation of team procedures and processes and
share with associates team members.share with associates team members.
 Handle Support Risk Assessment Team compliance activities, proactivelyHandle Support Risk Assessment Team compliance activities, proactively
prepare for logical reasons.prepare for logical reasons.
 Follow time schedules of each task per defined rulesFollow time schedules of each task per defined rules

13. Client’s Challenges
1. Understanding your Client
 Put yourself in your Client Shoes.
 Using Data to Understand your Client.
 Ask your Client what they think (Feedback).
 Go the extra mile for your Client.
2. Handling Customer Complaints.
 Get the Problem Fixed.
 Tell the World About it.
 Help the Company avoid similar problems in future.
3. Some points to consider when dealing with clients.
 Communication Strategy
 SOLER Magnet
 Be Positive

14. Q & AQ & A
SessionSession

15. Further Info:Further Info:
arsalan.aman@collabotive.comarsalan.aman@collabotive.com
Thank you for listening!Thank you for listening!