CSS 360 Midterm 2 Review
Requirements Engineering Answer- The process of establishing the services that the
customer requires from a system and the constraints under which it operates and is
developed.
Requirements Answer- The parameters placed on the development of a product or
system. The requirements include the safety needs, the physical laws that will limit the
development of an idea, the available resources, the cultural norms, and the use of
criteria and constraints.
Requirements Document Answer- Document which includes a needs statement, a
source of data, and a summary of calculations, often used as a contract between the
team and the customers.
Requirements Statement Answer- A consolidation of all system models, discovery
prototypes, and supporting documentation.
Scenario Answer- Real-life examples of how a system can be used, good for adding
details to outline requirements descriptions.
They include descriptions of the starting situation, descriptions of the normal flow of
events, descriptions of what should go wrong, information about the other concurrent
activities, and a description of the ending.
Requirements Identification Answer- How requirements are individually identified.
Identify the problem to be solved, the features of the solution, the business case, and
the acceptance criteria
Change Management Process Answer- The process followed when analyzing
requirements changes.
Traceability Answer- The capability to determine whether requirements are satisfied.
Concerned with the relationships between requirements, their sources, and the system's
design.
Traceability Policies Answer- The amount of information about requirements
relationships that is maintained - it tells users how traceability will be tested.
Requirements Traceability Matrix (RTM) Answer- A way to keep track of which
requirement is related to which testing. All requirements and test cases are identified
with numbers and letters here, respectively.
, Systems Engineering Answer- Applies engineering principles in designing and
managing large complicated projects.
Software Quality Answer- The totality of functionality and features of a software product
that bear on its ability to satisfy stated or implied needs.
Differences Between Software Engineering and Systems Engineering Answer- -
Systems engineering deals with all aspects of creating and maintaining complete
systems - hardware, software, infrastructure, operations, and everything else.
- Software engineering concentrates specifically on the software component of the
larger system.
- They are difficult to separate in software-dominated systems.
Systems Model Answer- A way to classify subsystems and components based on
functionality, location, and other factors.
Context Diagram Answer- A systems model where the shapes have specific meanings:
- The circle is the system being developed
- The arrows are data flows
- The boxes are external systems or data sources - every box needs to work in order for
the Intranet to work.
System Reliability Factors Answer- A set of factors that affect reliability. Some include
hardware and infrastructure, software errors, and human error, and external factors like
physical environment, operations, and business environments (enforcement, ethics,
etc.)
Separation of Concerns Answer- A way to deal with different aspects of a problem so
you can concentrate on and prioritize each part.
Abstraction Answer- A special case of separation of concerns. It is a process where
important aspects of phenomena are identified but their details are ignored. Examples in
code (usually for developers) and user interfaces (usually for users) - they represent the
same reality, the code in this case.
Information Hiding Answer- A special case of abstraction, treating modules in a system
as "black boxes," with inputs, outputs, and purposes all in one.
Modularity Answer- The breakdown of complex systems into simple pieces. Breaking
down into modules can enhance reusability, either in the next version or the next
product. The pieces are called modules.
Requirements Engineering Answer- The process of establishing the services that the
customer requires from a system and the constraints under which it operates and is
developed.
Requirements Answer- The parameters placed on the development of a product or
system. The requirements include the safety needs, the physical laws that will limit the
development of an idea, the available resources, the cultural norms, and the use of
criteria and constraints.
Requirements Document Answer- Document which includes a needs statement, a
source of data, and a summary of calculations, often used as a contract between the
team and the customers.
Requirements Statement Answer- A consolidation of all system models, discovery
prototypes, and supporting documentation.
Scenario Answer- Real-life examples of how a system can be used, good for adding
details to outline requirements descriptions.
They include descriptions of the starting situation, descriptions of the normal flow of
events, descriptions of what should go wrong, information about the other concurrent
activities, and a description of the ending.
Requirements Identification Answer- How requirements are individually identified.
Identify the problem to be solved, the features of the solution, the business case, and
the acceptance criteria
Change Management Process Answer- The process followed when analyzing
requirements changes.
Traceability Answer- The capability to determine whether requirements are satisfied.
Concerned with the relationships between requirements, their sources, and the system's
design.
Traceability Policies Answer- The amount of information about requirements
relationships that is maintained - it tells users how traceability will be tested.
Requirements Traceability Matrix (RTM) Answer- A way to keep track of which
requirement is related to which testing. All requirements and test cases are identified
with numbers and letters here, respectively.
, Systems Engineering Answer- Applies engineering principles in designing and
managing large complicated projects.
Software Quality Answer- The totality of functionality and features of a software product
that bear on its ability to satisfy stated or implied needs.
Differences Between Software Engineering and Systems Engineering Answer- -
Systems engineering deals with all aspects of creating and maintaining complete
systems - hardware, software, infrastructure, operations, and everything else.
- Software engineering concentrates specifically on the software component of the
larger system.
- They are difficult to separate in software-dominated systems.
Systems Model Answer- A way to classify subsystems and components based on
functionality, location, and other factors.
Context Diagram Answer- A systems model where the shapes have specific meanings:
- The circle is the system being developed
- The arrows are data flows
- The boxes are external systems or data sources - every box needs to work in order for
the Intranet to work.
System Reliability Factors Answer- A set of factors that affect reliability. Some include
hardware and infrastructure, software errors, and human error, and external factors like
physical environment, operations, and business environments (enforcement, ethics,
etc.)
Separation of Concerns Answer- A way to deal with different aspects of a problem so
you can concentrate on and prioritize each part.
Abstraction Answer- A special case of separation of concerns. It is a process where
important aspects of phenomena are identified but their details are ignored. Examples in
code (usually for developers) and user interfaces (usually for users) - they represent the
same reality, the code in this case.
Information Hiding Answer- A special case of abstraction, treating modules in a system
as "black boxes," with inputs, outputs, and purposes all in one.
Modularity Answer- The breakdown of complex systems into simple pieces. Breaking
down into modules can enhance reusability, either in the next version or the next
product. The pieces are called modules.
