DOC PREVIEW
UNCC ECGR 6185 - Project Capability and Requirements Guidelines

This preview shows page 1-2-3 out of 8 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 8 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 8 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 8 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 8 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

UNC Charlotte Senior Design Internal Use Only Page 1 of 8 For use by all projects Rev. B Guideline Document Author: James Conrad Date: 2007-02-05 Project Capability and Requirements Guidelines Date Rev Author Comments 2006-08-15 A J.M. Conrad Original Document 2007-02-05 B J.M. Conrad Minor change to page 6, 1st paragraph (“about”) Table of Contents 1 Overview................................................................................................................................. 1 2 Requirement Engineering ....................................................................................................... 1 2.1 Capabilities Gathering .................................................................................................... 1 2.2 Capabilities Demonstration Test Plan............................................................................. 2 2.3 Requirements Gathering ................................................................................................. 2 2.4 Requirements Analysis ................................................................................................... 2 2.5 Requirements Management ............................................................................................ 2 2.6 Requirements Verification – Acceptance Test Plan ....................................................... 3 2.7 Development Steps ......................................................................................................... 3 2.8 Using this Guideline for Requirements Refinement....................................................... 3 3 Writing Clear Requirements ................................................................................................... 4 3.1 Characteristics of a Good Requirement.......................................................................... 5 3.2 Types of Requirements ................................................................................................... 7 4 Capability and Requirements Steps ........................................................................................ 7 5 References............................................................................................................................... 8 1 Overview This document describes the steps a Principal Engineer (one of the team members) must follow to create and maintain a project’s Capability and Requirements and Acceptance Test Plan documents. 2 Requirement Engineering Requirements Engineering is the disciplined application of scientific principles and techniques for developing, communicating, and managing requirements [1]. Requirements will serve as the rubric by which Company ABC can verify that the end device has all the functionality the customer desires. To this end, the Principal Engineer (PE) will need to ensure the following tasks are followed. 2.1 Capabilities Gathering In this step, the PE will be responsible for gathering all information needed to document the capabilities. This includes [1]:UNC Charlotte Senior Design Internal Use Only Page 2 of 8 For use by all projects Rev. B Guideline Document Author: James Conrad Date: 2007-02-05 • Identifying relevant published sources of requirements (Statement of Work, Proposals, and BAAs/RFPs). • Interview/discuss with the customer specific capabilities 2.2 Capabilities Demonstration Test Plan The Demonstration Test Plan should describe the tests and test steps needed to demonstrate the capabilities of the device. Each test should indicate which capability is being verified. All capabilities must be verified by at least one test. 2.3 Requirements Gathering In this step, the PE will be responsible for gathering all information needed to document the requirements. This includes [1]: • Identifying relevant sources of requirements (capabilities, Statement of Work, Proposals, and people). • Determining what information is needed. • Analyzing the gathered information, looking for implications, inconsistencies, or unresolved issues. • Confirming the understanding of the requirements with the source. • Synthesizing appropriate statements of the requirements. 2.4 Requirements Analysis The next step will be to create and analyze all requirements. The PE will obtain requirements from all possible sources (include but not limited to) [1]: • Observation and measurements of the current system. • Interviews with customers. • Current system documentation. • Feasibility studies (Phase I reports). • Models and prototypes. • Analytical analysis. The Requirements Document, once written, must be approved by the customer (Company ABC technical employees and management) and the faculty mentor. Note that some requirements may be ill-defined or vague. These should be noted, and effort should be spent by the PE to investigate the technological area in order to make the requirements more clear BEFORE the design is started. 2.5 Requirements Management Once the requirement documents have been approved, there should be real proof that a change is necessary with a measurable benefit of the change. The clear responsibility is to keep project within costs, within budget, and to meet customer’s needs. Any change will need to go through an analysis to determine the impact (cost and time) of the proposed change. A requirement change must be accepted by the PE, and approved by the customer and the faculty mentor.UNC Charlotte Senior Design Internal Use Only Page 3 of 8 For use by all projects Rev. B Guideline Document Author: James Conrad Date: 2007-02-05 2.6 Requirements Verification – Acceptance Test Plan An Acceptance Test Plan will be written at the same time as the Requirements Document. The Test Plan will represent the steps needed to verify that the requirements have been met. Each test must verify at least one specific requirement. All requirements must be addressed by at least one test. The test plan will consist of specific tests, each with detailed test steps, and each noting which requirement has been addressed. 2.7 Development Steps The Figure 1 shows the simple steps which the design team will follow for project planning, design, and implementation. The requirements steps described in this document and the documents created are show in the top part of the figure. System RequirementsSystem


View Full Document

UNCC ECGR 6185 - Project Capability and Requirements Guidelines

Documents in this Course
Zigbee

Zigbee

33 pages

Load more
Download Project Capability and Requirements Guidelines
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Project Capability and Requirements Guidelines and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Project Capability and Requirements Guidelines 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?