What follows is in response to these problems. A standard set of documents used to express, requirements of all levels will be defined. An established set of requirement types to capture stakeholder problems, needed features of the system, software requirements, test requirements, standard terms and business rules will be described. For each requirement type a collection of requirements attributes, used to manage delivery of the needed system and manage changes to the requirements over the lifecycle of the project, will be identified along with values and ranges appropriate for each. A model of traces between requirements will be established to help communicate requirements change to all members of the project team. An initial list of predefined views of requirements information will be defined. This list must evolve with use. A set of tool extensions to provided needed functionality specifically for TGI will be created. Finally, a list of roles within the requirements management process will be identified.The premise of this endeavor from the start was that an initial process and tool configuration for requirements management be defined, and that these would evolve through use. This being the case, this document should be considered a “living” document and changes to it over time and experience are expected. Changes to this document should be made in a controlled manner and only after review by impacted groups. The project management strategy taken by TGI IT is one that places an emphasis on customer satisfaction. This plan embraces that strategy.
đang được dịch, vui lòng đợi..
