Your SlideShare is downloading. ×
0
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Software life cycle ppt
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software life cycle ppt

7,279

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
7,279
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Business analysis is a research discipline of identifying business needs and determining solutions to business problems. Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product. It is both Process and Product of Planning, Designing. The process of developing or being developed (RSM). It take measures to check the quality, performance, or reliability of (RSM), esp. before putting it into widespread use or practice, and ascertaining or fixing the value or worth of RSM. Making RSM available for Use. The routine functioning of RSM and maintaining the original state of RSM for as long as possible.
  • SRS – Software Requirement Specification SDLC – Software Development Life Cycle
  • SOLER Magnet– Straight, Open Posture, Lean Forward, Eye-Contact, Relaxed
  • Transcript

    1. Identifying Needs and EstablishingIdentifying Needs and EstablishingRequirementsRequirementsByBy –– Arsalan AmanArsalan AmanHow business process run live software with customHow business process run live software with customdevelopment & supportdevelopment & support
    2. 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 itshould 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 updatedaccordingly.accordingly.
    3. Why do we need Requirements?Why do we need Requirements? The requirements gathering process involves communication with topmanagement, managers, customers and sometimes end-users. After gatheringfunctional requirements for presentation, business logic and data layers the workon the software project is passed on to software architects, who will be taskedwith software design. Meetings with managers, stake holders and users are held in order to determinethe requirements like;• Who is going to use the system? How will they use the system? What should bethe 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 gatheringphase. After requirement gathering these requirements are analyzed for theirvalidity and the possibility of incorporating the requirements in the system to bedevelopment is also studied.
    4. Design By Application DevelopmentTeam 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, accuracyand 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 amaster plan, comparing the ongoing progress of the project requirements to itsmaster plan, comparing the ongoing progress of the project requirements to itsactual 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 structurethat can be implemented in a programming language. The output of the designthat can be implemented in a programming language. The output of the designphase 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.
    5. 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 iterationswhere the customer is asked to review works and provide feedback andwhere the customer is asked to review works and provide feedback andapprovals.approvals. Often during development, new issues may arise that are brought to lightOften during development, new issues may arise that are brought to lightthat were unforeseen and may affect items within the solution that will needthat were unforeseen and may affect items within the solution that will needto be addressed by proper consideration of all parties considered.to be addressed by proper consideration of all parties considered.
    6. DevelopmentDevelopment Typically these situations are minor and usually benefit the solution byTypically these situations are minor and usually benefit the solution byadding 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 ofdeveloping a unit or segment of the solution for functionality anddeveloping a unit or segment of the solution for functionality andcompleteness. These same tests will be performed in the QA stage butcompleteness. These same tests will be performed in the QA stage butDevelopers should test first themselves! Some time related issue fixed butDevelopers should test first themselves! Some time related issue fixed butimpact other system!!!!!impact other system!!!!!
    7. 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 measuresto ensure quality levels within a software development effort. The plan isto ensure quality levels within a software development effort. The plan isused as a baseline to compare the actual levels of quality duringused as a baseline to compare the actual levels of quality duringdevelopment with the planned levels of quality. If the levels of quality aredevelopment with the planned levels of quality. If the levels of quality arenot within the planned quality levels, management will respondnot within the planned quality levels, management will respondappropriately 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.
    8.  Deployment: After successful testing the product is delivered / deployed to the customer fortheir use.)) Re MeetingRe MeetingWe 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 clientHappy 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 doenhancement accordingly.enhancement accordingly.
    9. Application Development Team Application Development Team ResponsibilityResponsibilityWith the application tested and deployed into the clients workplace, the softwareenters into the Maintenance Phase of the SDLC. Even with the best attention todetail in the earlier phases, changes to the software may be necessary for a numberof 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 unforeseenbefore.Software bugs are almost inevitable. If enough bugs accumulate, releasing animproved version of the software may be in order.The business rules that were put in place at design time may change, necessitatingchanges in the software.
    10. 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, assignactivities, changes roles & updates activities with multi reports andactivities, changes roles & updates activities with multi reports andmeetings 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 matcheither 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.
    11. Business Process & SupportBusiness Process & SupportResponsibilityResponsibility Deliver and drive new processes within Support organization and reworkDeliver and drive new processes within Support organization and reworkwith 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 andautomate 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 alllevels.levels. Create and manage documentation of team procedures and processes andCreate and manage documentation of team procedures and processes andshare with associates team members.share with associates team members. Handle Support Risk Assessment Team compliance activities, proactivelyHandle Support Risk Assessment Team compliance activities, proactivelyprepare for logical reasons.prepare for logical reasons. Follow time schedules of each task per defined rulesFollow time schedules of each task per defined rules
    12. 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
    13. Q & AQ & ASessionSession
    14. Further Info:Further Info:arsalan.aman@collabotive.comarsalan.aman@collabotive.comThank you for listening!Thank you for listening!

    ×