logging in or signing up Software Requirement Specification aSGuest75867 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: Embed: Flash iPad Copy Does not support media & animations WordPress Embed Customize Embed URL: Copy Thumbnail: Copy The presentation is successfully added In Your Favorites. Views: 2784 Category: Entertainment License: All Rights Reserved Like it (1) Dislike it (0) Added: November 19, 2010 This Presentation is Public Favorites: 2 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Slide 1: The customer in developing the software requirements Don’t use computerese – customers do not speak your language problem domain – the customer knows this far better than you do You should have no loyalty to a particular solution. You are problem solving! Software Requirements Specification Software Requirements Specification : Software Requirements Specification Should set out what the system should do without specifying how it should be done. One-to-one mapping from software requirements document onto the final system design. Software Requirements Specification : Software Requirements Specification Identifying need is the starting point in the evolution of a computer based system. A BA assists the customer in defining the goals of the system (product) What information will be produced? What information is to be provided? What functions and performances are required? How do we gather Requirements? : How do we gather Requirements? Observation - Watch Interview – Listen Research - Learn Characteristics of “good” business requirements. : Characteristics of “good” business requirements. 1. They are precise, with no room for misinterpretation by customers, users or implementers. 2. They specify just what the system must do, NOT how to do it. 3. They show conceptual integrity (a set of facilities that interact well with each other). Project Plan Must Be Complete! : Project Plan Must Be Complete! Missing information represents errors by omission! Checklists help Select clear-cut, rational, measurable goals for the product and process Software Requirements Specification : Software Requirements Specification Distinguishes between Customer "needs" -- AND Customer's "wants" -- The Interview Process : The Interview Process not everything spoken is the truth sometimes people lie or forget facts most often they speak from their own ignorance or point of view interview many people to balanced information evaluate what you are hearing watch body language The Interview Process : The Interview Process Provide feedback What is it I heard? What do I understand? Rephrase critical information Ask the same question in a slightly different way, do you get the same response? What happens after the interview? : What happens after the interview? Immediately write down interview results. Research show that even in a life-and-death situations: 50% of what took place is forgotten within 30 minutes. Follow-up Memo Managing the Customer Expect the following: : Managing the Customer Expect the following: We don’t like your design. We would prefer you do it this way… (perhaps because this is how it has always been done….) We don’t like the steps you took in your source code. We would prefer you do it this way… And, when you follow their direction: What do you mean it doesn’t work? You’re the expert, why didn’t you talk us out of it? Managing the Customer : Managing the Customer Never lie - about schedule, budget, capabilities; to win the job, keep the job, or enhance your standing. Keep the customer appraised relentlessly - every week, every change, every problem, every success. Requirements creep : Requirements creep After the requirements have been agreed to, after design has occurred, during coding: The customer calls and has Additions that MUST be made Suggested changes to existing requirements New information that somehow that was left out of earlier discussions Prioritization : Prioritization users are likely to ask for the moon if there are no limits. beauty should not outweigh functionality. help customer be realistic about expectations. useful to identify enhancements for future work once basic product is developed. Requirements evolution : Requirements evolution The time required to analyze requirements and to develop a large system may be several years.Over that time.... The system's environment and the business objectives will almost certainly change. Constraints will be affected by changes in hardware technology. Hardware will improve. Anticipate hardware improvements while the software is being developed. . Changes during the projects LIFETIME should be assumed. Constraints will have to be modified while the software is in use. Requirements evolution : Requirements evolution The Software requirements document should be easy to change : Otherwise changes made not recorded system and specification are inconsistent maintenance problems Summary : Summary Accuracy Speed Integrity Innovation Optimization These are the key to success for any BA You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.