Procuring quality business requirements is an important step toward the design o

Question

Procuring quality business requirements is an important step toward the design of quality information systems. Completion of a quality requirements document allows user needs and expectations to be captured so that infrastructure and information systems can be designed properly. Using the requirements document provided in the course shell, you are to speculate on the needs of the company. You must consider current and future requirements; however, assumptions should be realistic and carefully considered.

a. Describe the project including the following:

   i. Describe the scope and analyze how to control the scope.

    ii. Identify possible risks, constraints, and assumptions.

    iii. Describe the integration with other systems and infrastructure. Note: Database and interface design, security, and networking should be considered.

    iv. Define relevant terms that will be used throughout project

Explanation / Answer

Project Scope:

            A project scope, or project scope statement, is a tool used to describe the major deliverables of a project including the key milestones, high level requirements, assumptions, and constraints. The documentation of a project's scope explains the boundaries of the project, establishes responsibilities for each team member and sets up procedures for how completed work will be verified and approved.

                A poorly defined scope is one of the main causes of project failures. If the project does not satisfy the real needs of a customer it is doomed to fail. An incomplete scope will not cover all the needs and issues to be addressed.

Project Control Scope:

            Scope Control is the process of controlling changes the project scope is the a project management activity of monitoring the status of the project, finding whether the deliverables meet documented requirements, and managing changes to project scope baseline.

            The project management plan, specifically the scope baseline, which is the ‘expected scope’ against which implemented scope of the project is compared and variance, is calculated.

            Scope change is bound to happen and is expected in most cases, but the goal is to keep your scope as focused as possible in hopes of creating as straight of a line to you and your client's goal as possible. If a projects scope is clearly identified and properly associated to the resources, time and budget throughout the project lifespan the likelihood for success is greatly improved. Allowing your scope to move around like a ducks head may get you to your goal eventually, but not very efficiently.

Identify possible risks, constraints, and assumptions.

Risks

            A risk is might prevent project goal or prevent completion of the project, or perhaps could adversely affect the design. Risks are common place in every project and should be identified early to eliminate any aspect of surprise.

Clearly identify and list every risk that might prevent further progress.

Assumptions

            An assumption is something that will be true to the project design, but is something that has not been fully tested nor verified. Assumptions can impact any part of your project life cycle and resulting solution implementation, so it is important to document and analyze them.

Constraints

            A constraint is something that plays the part of a restriction or limitation. It could well limit a design choice. Much like a requirement, a constraint can be of business or technical focus. Business constraints limit the solution based upon the current organizational state. They usually focus on the available time, money and resources for a project. Common business constraints include budget and time restrictions, resource limitations, and resource skill limitations.

Constraints could be a business policy or a technical limitation that is limiting the design choice.

Integration with other systems and infrastructures

            Integration is the act of bringing together smaller components into a single system that functions as one. In an IT context, integration refers to the end result of a process that aims to stitch together different, often disparate, subsystems so that the data contained in each becomes part of a larger, more comprehensive system that, ideally, quickly and easily shares data when needed. The aggregation of different component systems or subsystems that cooperate to deliver a whole functionality has been the focus of industries that use technology. This is known as the modular approach to systems building, and the SI process has always been at the near-end of the development cycle.

Define relevant terms that will be used throughout project

            Project management can be concerned with anything, particularly introducing or changing things, in any area or function,

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.