New Semester
Started
Get
50% OFF
Study Help!
--h --m --s
Claim Now
Question Answers
Textbooks
Find textbooks, questions and answers
Oops, something went wrong!
Change your search query and then try again
S
Books
FREE
Study Help
Expert Questions
Accounting
General Management
Mathematics
Finance
Organizational Behaviour
Law
Physics
Operating System
Management Leadership
Sociology
Programming
Marketing
Database
Computer Network
Economics
Textbooks Solutions
Accounting
Managerial Accounting
Management Leadership
Cost Accounting
Statistics
Business Law
Corporate Finance
Finance
Economics
Auditing
Tutors
Online Tutors
Find a Tutor
Hire a Tutor
Become a Tutor
AI Tutor
AI Study Planner
NEW
Sell Books
Search
Search
Sign In
Register
study help
business
organization theory and design
System Analysis Design And Development: Concepts Principles And Practices 1st Edition Charles S. Wasson - Solutions
If the system has UTILITY to the organization, is SUITABLE for the application, and is AVAILABLE to perform its mission when tasked, will it be EFFECTIVE in performing mission and accomplishing mission objectives with a required level of success?
If the system has UTILITY and is SUITABLE for the application, will it be operationally AVAILABLE to perform the mission when tasked?
If the system has UTILITY, will it be SUITABLE for the User’s mission application(s) and integrate easily into their business model?
If we invest in the development of this system, product or service, will it have UTILITY to the User in accomplishing their organizational missions?
Contact a contract program within your organization.(a) What types of specification review methods were used to review specification requirements?(b) What guidance did the program provide to specification developers regarding requirements development guidelines or criteria?
Research your organization’s command media for guidance or direction in preparing requirements statements.Document your findings.
Select a contract specification or one developed by your organization and test it using the criteria described in this section.
HOW is the outcome to be measured and verified.
WHAT are the expected result(s) and outcome(s).
WHO is the expected recipient(s) of the action.
WHEN the capability or action is to be initiated.
WHAT by-products are to be AVOIDED.
WHAT is expected as a performance-based outcome (i.e., WHAT products or services are to be produced).
WHAT scenario or conditions for performing the action.
The source of the action.
The use case based operational capability to the performed.
How do you minimize requirements?
What is requirements minimization?
What is a Requirements Verification Matrix (RVM)?
How do you identify a requirement’s verification method(s)?
What criteria do you use to “test” a requirement?
What methodology should one use to create a requirements statement?
What is a common pitfall in preparing requirements statements?
What are some suggestions for preparing “good” requirements?
What are the attributes of a “good” requirement?
Contact a contract program within your organization and interview the Technical Director, Project Engineer, and Lead SEs to answer the following questions:(a) How were requirements derived?(b) Did the contract mandate traceability of requirements?(c) Did the program use a requirements management
Research your organization’s command media. What guidance and direction is provided for deriving, allocating, flowing down, and tracing requirements?
What the User is WILLING to pay.
What the User can AFFORD.
What the User WANTs.
What the User NEEDs.
WHAT is the relationship of this capability to others?
Under WHAT scenarios and conditions should each capability be performed?
HOW WELL must each required capability be performed?
WHEN is the capability to be provided to achieve the desired outcome?
WHAT outcomes must be achieved to satisfy this requirement?
Research your organization’s command media. What guidance or direction is provided concerning development of specifications and approaches?
Contact several contract programs within your organization. Interview the Technical Director, Project/Chief Engineer, or lead SEs and answer the following questions:(a) What type of specifications are required by the contract?(b) How was each specification developed—by feature-based, reuse, or
What is the model-based development approach to specification development?
What is the architecture-based specification development approach?
What about training?
Any other constraints concerning the way the SYSTEM/entity is to be designed and constructed?
Any special considerations about safety?
Any weight restrictions?
Identify the system’s interfaces?
What functions should the SYSTEM/entity perform?
What are its modes and states of operation?
What is the system’s mission?
Identify the SYSTEM OF INTEREST (SOI).
Contact several contract programs within your organization. Interview the Technical Director, Project Engineer, or Lead SEs to answer the following questions:(a) How were system requirements analyzed during the proposal effort that culminated in the development of the program’s System Performance
Research your organization’s command media. What guidance or requirements are levied on contract programs concerning specification analysis? Document your findings.
Are there any obvious “holes” in the graphic that are not specified as requirements in the specification?
Based on the requirements, as stated, can we draw a simple graphic of the system and its interactions with its OPERATING ENVIRONMENT?
Are there any “holes” in the set of requirements?
Are the requirements positioned and scoped at the right levels?
Are there any misplaced, overlapping, duplicated, or conflicting requirements?
Are there any critical operational or technical issues (COIs/CTIs) that require resolution or clarification?
Are there any TBDs remaining in the specification?
Are all system interface requirements identified?
Do the requirements unnecessarily CONSTRAIN the range of viable solutions?
Do the requirements adequately capture User operational needs? Are they necessary and sufficient?
Do the requirements appear to have been written by a seasoned subject matter expert (SME)or semi-knowledgeable person?
Do the requirements follow standard guidelines discussed later in Requirements Statement Development Practices?
Do the list of requirements appear to be generated as a feature-based “wish list” or reflect structured analysis?
Do these requirements mandate technologies that pose unacceptable risks?
Can the requirements, as stated, be verified within reasonable expectations, cost, schedule, and risk?
Do we understand the problem the User is attempting to solve by procuring this system?Does the specification bound the problem or a symption of the problem?
Have we thoroughly investigated and talked with a representative cross section of the User community to validate their requirements and needs?
Do the system requirements, as stated, specify a system that satisfies the User’s operational needs? If not, what approach must we use to inform them?
Do we fully understand the scope of the effort we are signing up to perform?
Can the system specified be developed within the total life cycle cost—such as acquisition, operations and support (O&S), and retirement costs—budgets that are available?
If we procure a system based on these requirements, will the deliverable product satisfy the User’s intended operational needs?
Does this specification adequately, accurately, and precisely specify the selected solution space?
Have we identified the RIGHT system to fill the prescribed solution space and cope with OPERATING ENVIRONMENT?
Have we bounded the CORRECT solution space within the problem space?
Have all User System Deployment Phase, System Operations and Support (O&S) Phase, and System Disposal Phase stakeholder requirements been adequately identified, prioritized, scoped, and specified?
When requirements deficiencies are identified, how should you resolve them?
What are some common types of specification requirements deficiencies?
For a contract program, identify who the SPS stakeholders are based on the specified requirements. Based on those stakeholders, prioritize them in terms of an estimate based on requirements count.
Research contract specifications and identify those that specify the precedence of requirements for decision making.
Select a specification on a contract program for analysis. Using the concepts discussed in this chapter, as a consultant to the specification developer, identify defects and deficiencies in the specification and suggest recommendations for improvement.
What types of metrics are used to track specification defects and deficiencies?
What lessons learned did program personnel learn in the following areas and how did they resolve the issue?(a) Missing requirements(b) Misplaced requirements(c) Conflicting requirements(d) Duplicated requirements(e) Nonfunctional requirements(f ) Verification requirements
Interview program technical management and SEs. How were requirements in the System Performance Specification (SPS) elicited and collected from stakeholders? Document your findings and observations?
Contact several contract programs within your organization. Request an opportunity to analyze the System Performance Specification (SPS) for each program and answer the following questions:(a) Identify five examples of operational requirements.(b) Identify five examples of capability
Contact a contract program within your organization.(a) What specifications are required to be delivered as Contract Data Requirements List (CDRL) items?(b) What delivery requirements are levied on the program specification CDRL deliveries during the System Development Phase?(c) Does the program
Research your organization’s command media for guidance concerning development of specifications.(a) What requirements do the command media impose on contract programs?(b) What does the media specify about timing for developing and approving specifications?
HOW did you document WHAT you agreed to?
WHEN did you discuss it?
WHERE did you discuss the matter?
WHO did you talk to?
WHAT did you specify via the contract, meeting minutes, official correspondence, conversations, etc.?
HOW does a specification accomplish a specific objective?
WHAT is the purpose of a specification?
What is the standard format for most specifications?
How is the specification tree structured?
What is a specification tree?
Describe the evolution of specifications from initial system concept to System Performance Specification (SPS).
What makes a “good” specification?
Contact two or three contract development programs within your organization.(a) Interview key personnel to discuss the type(s) of development strategies that were employed and the rationale for each.(b) Document and report your results.
Showing 1800 - 1900
of 2629
First
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
Last
Step by Step Answers
Get 50% OFF
Claim Now
