Identifying Needs and Establishing Identifying Needs and Establishing RequirementsRequirements

By By –– Arsalan Aman Arsalan Aman

How business process run live software with custom How business process run live software with custom development & supportdevelopment & support

What are requirements?What are requirements?

A requirement is a statement about an intended product that specifies what it A 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 updated System & process support changes frequently so Software should be updated accordingly.accordingly.

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.

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, accuracy Data 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 a This specification document is then used by the design and development teams as a master plan, comparing the ongoing progress of the project requirements to its master 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 structure Includes translation of the requirements specified in the SRS into a logical structure that can be implemented in a programming language. The output of the design that can be implemented in a programming language. The output of the design phase is a design document that acts as an input for all phase is a design document that acts as an input for all

the subsequent SDLC phases.the subsequent SDLC phases.

DevelopmentDevelopment

This is where the solution begins to be developed. There may be iterations This is where the solution begins to be developed. There may be iterations where the customer is asked to review works and provide feedback and where the customer is asked to review works and provide feedback and approvals.approvals.

Often during development, new issues may arise that are brought to light Often during development, new issues may arise that are brought to light that were unforeseen and may affect items within the solution that will need that 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.

DevelopmentDevelopment

Typically these situations are minor and usually benefit the solution by Typically 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 of Unit testing is performed during development as it pertains to the nature of developing a unit or segment of the solution for functionality and developing a unit or segment of the solution for functionality and completeness. These same tests will be performed in the QA stage but completeness. These same tests will be performed in the QA stage but Developers should test first themselves! Some time related issue fixed but Developers should test first themselves! Some time related issue fixed but impact other system!!!!!impact other system!!!!!

Testing & Evaluation - Q.A Testing & Evaluation - Q.A The software quality assurance (SQA) plan is an outline of quality measures The software quality assurance (SQA) plan is an outline of quality measures

to ensure quality levels within a software development effort. The plan is to ensure quality levels within a software development effort. The plan is used as a baseline to compare the actual levels of quality during used as a baseline to compare the actual levels of quality during development with the planned levels of quality. If the levels of quality are development with the planned levels of quality. If the levels of quality are not within the planned quality levels, management will respond not 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.

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 client We 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 do Happy or some time client change his requirement so we priorities it or do enhancement accordingly.enhancement accordingly.

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.

Business Process & Support Business Process & Support ResponsibilityResponsibility

Engage in daily responses of system process like, sales data sync, assign Engage in daily responses of system process like, sales data sync, assign activities, changes roles & updates activities with multi reports and activities, 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 match Follow 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 and Analyses reports per client requirement and reviews for direct reports. reviews for direct reports.

Business Process & Support Business Process & Support ResponsibilityResponsibility

Deliver and drive new processes within Support organization and rework Deliver 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 and Contribute 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 all Communicate system updates with business partners and associates at all levels. levels.

Create and manage documentation of team procedures and processes and Create 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, proactively Handle 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

Client’s Challenges1. 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

Q & AQ & ASessionSession

Further Info:Further Info:

arsalan.aman@collabotive.comarsalan.aman@collabotive.com

Thank you for listening!Thank you for listening!