UH Software Design Review. Chapters 1-5 (Test 1)
A non-functional requirement deals with all of these except a) performance b) security c) quality d) functional requirement
functional requirement
Ask a set of questions that establish basic understanding of the problem is known as
inception
Software development process that develops software iteratively with a heavy emphasis on construction activities is known as
Agile
7 Principles of Software Engineering
(1) The reason it all exists (2) KISS: Keep it simple, stupid (3) Maintain the vision (4) What you produce, others will consume (5) Be open to the future (6) Plan ahead for resuse (7) Think!
Umbrella Activities
- Software project tracking and control - Risk management - Software quality assurance - Technical reviews - Measurement - Software configuration management - Reusability management - Work product preparation and production
ISO 9001:2000 for Software
A generic standard that applies to any organization that wants to improve the overall quality of the products, systems, or services that it provides. Therefore, the standard is directly applicable to software organizations and companies.
Process Pattern
A process related problem that is encountered during software engineering work, identifies the environment in which the problem is encountered, and suggest s that one or more solutions to the problem. - Pattern name - Intent - Pattern type + Stage + Task + Phase - Initial context - Problem - Solution - Resulting context - Related patterns - Known uses and examples
Prototyping (Evolutionary Process Model)
A technique that can be used with any process model, where a quick prototype of the software is built for defining requirements and then discarded.
These are all agile development methods except a) waterfall b) scrum c) XP D) TDO
A) waterfall
Spiral Model (Evolutionary Process Model)
Can be adopted to apply throughout the entire life cycle of an application, from concept development to maintenance
Other Process Models
Component based development—the process to apply when reuse is a development objective Formal methods—emphasizes the mathematical specification of requirements AOSD—provides a process and methodological approach for defining, specifying, designing, and constructing aspects Unified Process—a "use-case driven, architecture-centric, iterative and incremental" software process closely aligned with the Unified Modeling Language (UML)
Code is generated, reviewed, compiled and tested in what stage of personal software process
Development
Evolutionary Model
Evolutionary process models produce an increasingly more complete version of the software with each iteration.
(True / False) A familiar context makes software hard to use
F
(True / False) Anyone allowed to access secured content of a web app
F
(True / False) Requirements are always one way, there is no room for negotiation
F
V-Model (Prescriptive Process Model)
Like the waterfall model, but arranged in a V-shape, showing the relationship between an early phase and a testing phase. There is a greater emphasis on testing, and testing procedures are developed early on.
Waterfall Method (Prescriptive Process Model)
Method in which the systems development life cycle tasks occur sequentially, with one activity starting only after the previous one has been completed. Shortcomings: (1) Real projects rarely follow the sequential flow that the model process proposes (2) Customers don't or can't state all requirement explicitly, doesn't accommodate natural uncertainty that exists at beginning of projects (3) Working version of the program isn't available to customers until later in the project time span
Prescriptive Process Models
Prescriptive process models advocate an orderly approach to software engineering That leads to a few questions ... If prescriptive process models strive for structure and order, are they inappropriate for a software world that thrives on change? Yet, if we reject traditional process models (and the order they imply) and replace them with something less structured, do we make it impossible to achieve coordination and coherence in software work?
CMM-Based Appraisal for Internal Process Improvement (CBA IPI)
Provides a diagnostic technique for assessing the relative maturity of a software organization; uses the SEI CMM as the basis for the assessment
Standard CMMI Assessment Method for Process Improvement (SCAMPI)
Provides a five step process assessment model that incorporates five phases: initiating, diagnosing, establishing, acting and learning.
Software development process where risk analysis is performed at regular stages in development cycle is known as
Spiral
(True / False) Agile adapts to change
T
(True / False) Analysis and design should always emphasize separation of concerns
T
(True / False) Cloud computing requires an architecture containing frontend and backend services
T
(True / False) Continuous attention to technical excellence and good design enhances agility.
T
(True / False) Design should be traceable to the requirements model
T
(True / False) Inception is one of the requirements engineering principal
T
(True / False) Legacy software may always not be able to implement new business requirements
T
(True / False) MobileApps require a different design compared to webapps
T
(True / False) Prescriptive process models advocate an orderly approach to software engineering
T
(True / False) Quality attribute, performance attribute, security attribute, or general system constraint are non-functional requirements
T
(True / False) Software must be re-architected to make it viable within a network environment
T
(True / False) Software should exhibit high quality
T
(True / False) Technical reviews help build high quality software
T
(True / False) Use case are important part of validating the requirements
T
(True / False) cloud architectures can be segmented to restrict access to private data
T
(True / False) mobileapps reside on mobile platforms such as cell phones or tablets
T
(True / False) modern webapps are much more than hypertext files with a few pictures
T
(True / False) software should be maintainable
T
1. (True/False) Legacy software may always not be able to implement business requirements
T
2. (True/False) Mobile apps reside on mobile platforms such as cellphones or tablets
T
3. (True/False) Cloud computing requires an architecture requiring front end and back end services
T
5. (True/False) Agile adapts to the change
T
7. (True/False)Software should be maintainable
T
True / False) Requirements analysis allows the software engineer to elaborate on basic requirements established during earlier requirement engineering tasks
T
Task Set
Task set defines the actual work to be done to accomplish the objectives of a software engineering action
SPICE
The SPICE (ISO/EC15504) standard defines a set of requirements for software process assessment. The intent of the standard is to assist organizations in developing an objective evaluation of the efficacy of any defined software process.
Concurrent Model (Evolutionary Process Model)
The concurrent development model, sometimes called concurrent engineering, allows a software team to represent iterative and concurrent elements of any of the process models described in this chapter.
Incremental Model (Prescriptive Process Model)
The incremental model delivers a series of releases, called increments, that provide progressively more functionality for the customer as each increment is delivered.
5 Process Framework Activities
[C]ommunication [P]lanning [M]odeling [C]onstruction [D]eployment
Types of Process Flows
[L]inear process flow [I]terative process flow [E]volutionary process flow [P]arallel process flow
4 Layers of Software Engineering
[T]ools [M]ethods [P]rocess [Q]uality Focus
4. Software development process where each phase is dependent on previous step is a.) waterfall b.) rapid c.) spiral
a.) waterfall
The benefit of software engineering using the cloud is
access to all software engineering work products
What is NOT software a) Instructions b) hardware c) data structures d) documentation
b) hardware
These are all effective software team attributes except a) sense of purpose b) sense of urgency c) sense of trust d) sense of involvement
b) sense of urgency
These are all Agile Methodologies except a) XP b) scrum c) SDD d) TDD
c) SDD
What is NOT agility a) response to change b) incremental delivery c) rigid model d) flexible model
c) rigid model
6. What is not agility a. A response to change b. Incremental delivery c. Rigid model d. Flexible model
c. Rigid model
Distributed data storage and processing resources to networked computing devices is known as
cloud computing
A process pattern that define the sequence of framework activities that occur with the process, even when the overall flow of activities is iterative in nature is known as
phase pattern
The application of a systematic, disciplined, and quantifiable approach to the development, operation, and maintenance of software is known as
software engineering
A process pattern that defines a problem associated with a framework activity for the process is known as
stage pattern
A scenario that describes a "thread of usage" for a system is known as
use case
A review mechanism that looks for missing information is known as
validation
Software development process where each phase is dependent on previous steps is known as
waterfall