Requirements Engineering Questions And
Answers 100% Verified.
The .'essential' .requirements .process .- .correct .answer. . . . .1. .Understand .the .problem
2. .Model .and .Analyze .the .problem
3. .Attain .agreement .on .the .nature .of .the .problem
4. .Communicate .the .problem
5. .Manage .change .as .the .problem .evolves
Understand .the .problem .- .correct .answer. . . . .• .use .data .gathering .techniques .to .elicit
.requirements
• .Eg. .Interviews, .Questionnaires, .Focus .Groups, .Prototyping, .Observation,...
Model .and .Analyze .the .problem .- .correct .answer. . . . .• .use .some .modeling .method(s)
• .Eg. .Structured .Analysis, .Object .Oriented .Analysis, .Formal .Analysis,...
Attain .agreement .on .the .nature .of .the .problem .- .correct .answer. . . . .• .validation
• .conflict .resolution, .negotiation
Communicate .the .problem .- .correct .answer. . . . .• .specifications, .documentation, .review
.meetings,
Manage .change .as .the .problem .evolves .- .correct .answer. . . . .• .Requirements .continue .to
.evolve .throughout .software .development
• .(introducing .new .software .changes .the .problem!!!)
• .requirements .management .- .maintain .the .agreement!
requirements .should .specify .___ .but .not .___ .- .correct .answer. . . . .what, .how
'What' .- .correct .answer. . . . .refers .to .a .system's .purpose
• .it .is .external .to .the .system
• .it .is .a .property .of .the .application .domain
'How' .- .correct .answer. . . . .refers .to .a .system's .structure .and .behavior
• .it .is .internal .to .the .system
• .it .is .a .property .of .the .machine .domain
,Requirements .only .exist .in .the .application .domain .- .correct .answer. . . . .- .Distinguishing
.between .the .machine .and .the .application .domain .is .essential .for .good .requirements
.engineering
- .Need .to .draw .a .boundary .around .the .application .domain
• .I.e. .which .things .are .part .of .the .problem .you .are .analyzing .and .which .are .not?
What .is .a .Requirement? .- .correct .answer. . . . .• .A .requirement .is .a .statement .of .one .of .the
.following:
- .1. .What .a .system .must .do
- .2. .A .known .limitation .or .constraint .on .resources .or
design
- .3. .How .well .the .system .must .do .what .it .does
Functional .Requirements .- .correct .answer. . . . .What .a .system .must .do
Non-
Functional .Requirements .(NFRs) .- .correct .answer. . . . .- .2. .A .known .limitation .or .constraint
.on .resources .or
design
- .3. .How .well .the .system .must .do .what .it .does
Requirements .engineering .- .correct .answer. . . . .• .The .process .of .establishing .the .services
.that .the .customer .requires .from .a .system .and .the .constraints .under .which .it .operates .and
.is .developed.
• .The .requirements .themselves .are .the .descriptions .of .the .system .services .and
.constraints .that .are .generated .during .the .requirements .engineering .process.
requirement .may .range .from .a .___ .of .a .service .or .of .a .___ .to .a .detailed .mathematical
.functional .specification. .- .correct .answer. . . . .high-level .abstract .statement, .system
.constraint
Software .Management .is... .- .correct .answer. . . . .• .A .systematic .approach .to .eliciting,
.organizing, .and .documenting .the .requirements .of .the .system, .and .a .process .that
.establishes .and .maintains .agreement .between .the .customer .and .the .project .team .on .the
.changing .requirement .of .the .system.
Types .of .requirement .- .correct .answer. . . . .• .User .requirements
• .System .requirements
Stakeholders .in .the .Mentcare .system .- .correct .answer. . . . .• .Patients .whose .information .is
.recorded .in .the .system.
• .Doctors .who .are .responsible .for .assessing .and .treating .patients.
• .Nurses .who .coordinate .the .consultations .with .doctors .and .administer .some .treatments.
• .Medical .receptionists .who .manage .patients' .appointments.
• .IT .staff .who .are .responsible .for .installing .and .maintaining .the .system.
, Agile .methods .and .requirements .- .correct .answer. . . . .• .Many .agile .methods .argue .that
.producing .detailed .system .requirements .is .a .waste .of .time .as .requirements .change .so
.quickly.
• .The .requirements .document .is .therefore .always .out .of .date.
• .Agile .methods .usually .use .incremental .requirements .engineering .and .may .express
.requirements .as .'user .stories' .(discussed .in .Chapter .3).
• .This .is .practical .for .business .systems .but .problematic .for .systems .that .require .pre-
delivery .analysis .(e.g. .critical .systems) .or .systems .developed .by .several .teams.
Functional .requirements .- .correct .answer. . . . .- .Statements .of .services .the .system .should
.provide, .how .the .system .should .react .to .particular .inputs .and .how .the .system .should
.behave .in .particular .situations.
Non-functional .requirements .- .correct .answer. . . . .- .constraints .on .the .services .or .functions
.offered .by .the .system .such .as .timing .constraints, .constraints .on .the .development
.process, .standards, .etc.
Domain .requirements .- .correct .answer. . . . .- .Requirements .that .come .from .the .application
.domain .of .the .system .and .that .reflect .characteristics .of .that .domain.
Functional .requirements .- .correct .answer. . . . .• .Describe .functionality .or .system .services.
• .Depend .on .the .type .of .software, .expected .users .and .the .type .of .system .where .the
.software .is .used.
• .Functional .user .requirements .may .be .high- .level .statements .of .what .the .system .should
.do
• .Functional .system .requirements .should .describe .the .system .services .in .detail.
functional .requirements .examples .- .correct .answer. . . . .- .E.g. .mapping .of .inputs .to .outputs
- .E.g. .control .sequencing
- .E.g. .timing .of .functions
- .E.g. .handling .of .exceptional .situations
- .E.g. .formats .of .input .and .output .data .(and .stored
data?)
- .E.g. .real .world .entities .and .relationships .modeled .by .the .system
- .Add .Participant
• ."The .software .shall .display .an .option .to .add .a .participant" .- .Summon .Operator
• ."The .software .shall .summon .the .operator .if .the .participant .clicks .the .Operator .Help .icon.
A .Functional .Requirement... .- .correct .answer. . . . .- .is .a .statement .of .what .a .system .must .do
.(#1) .- .is .measured .in ."yes" .or ."no" .terms
- .usually .employs .the .word ."shall"
The .LIBSYS .system .- .correct .answer. . . . .• .A .library .system .that .provides .a .single .interface
.to .a .number .of .databases .of .articles .in .different .libraries.
• .Users .can .search .for, .download .and .print .these .articles .for .personal .study.
Answers 100% Verified.
The .'essential' .requirements .process .- .correct .answer. . . . .1. .Understand .the .problem
2. .Model .and .Analyze .the .problem
3. .Attain .agreement .on .the .nature .of .the .problem
4. .Communicate .the .problem
5. .Manage .change .as .the .problem .evolves
Understand .the .problem .- .correct .answer. . . . .• .use .data .gathering .techniques .to .elicit
.requirements
• .Eg. .Interviews, .Questionnaires, .Focus .Groups, .Prototyping, .Observation,...
Model .and .Analyze .the .problem .- .correct .answer. . . . .• .use .some .modeling .method(s)
• .Eg. .Structured .Analysis, .Object .Oriented .Analysis, .Formal .Analysis,...
Attain .agreement .on .the .nature .of .the .problem .- .correct .answer. . . . .• .validation
• .conflict .resolution, .negotiation
Communicate .the .problem .- .correct .answer. . . . .• .specifications, .documentation, .review
.meetings,
Manage .change .as .the .problem .evolves .- .correct .answer. . . . .• .Requirements .continue .to
.evolve .throughout .software .development
• .(introducing .new .software .changes .the .problem!!!)
• .requirements .management .- .maintain .the .agreement!
requirements .should .specify .___ .but .not .___ .- .correct .answer. . . . .what, .how
'What' .- .correct .answer. . . . .refers .to .a .system's .purpose
• .it .is .external .to .the .system
• .it .is .a .property .of .the .application .domain
'How' .- .correct .answer. . . . .refers .to .a .system's .structure .and .behavior
• .it .is .internal .to .the .system
• .it .is .a .property .of .the .machine .domain
,Requirements .only .exist .in .the .application .domain .- .correct .answer. . . . .- .Distinguishing
.between .the .machine .and .the .application .domain .is .essential .for .good .requirements
.engineering
- .Need .to .draw .a .boundary .around .the .application .domain
• .I.e. .which .things .are .part .of .the .problem .you .are .analyzing .and .which .are .not?
What .is .a .Requirement? .- .correct .answer. . . . .• .A .requirement .is .a .statement .of .one .of .the
.following:
- .1. .What .a .system .must .do
- .2. .A .known .limitation .or .constraint .on .resources .or
design
- .3. .How .well .the .system .must .do .what .it .does
Functional .Requirements .- .correct .answer. . . . .What .a .system .must .do
Non-
Functional .Requirements .(NFRs) .- .correct .answer. . . . .- .2. .A .known .limitation .or .constraint
.on .resources .or
design
- .3. .How .well .the .system .must .do .what .it .does
Requirements .engineering .- .correct .answer. . . . .• .The .process .of .establishing .the .services
.that .the .customer .requires .from .a .system .and .the .constraints .under .which .it .operates .and
.is .developed.
• .The .requirements .themselves .are .the .descriptions .of .the .system .services .and
.constraints .that .are .generated .during .the .requirements .engineering .process.
requirement .may .range .from .a .___ .of .a .service .or .of .a .___ .to .a .detailed .mathematical
.functional .specification. .- .correct .answer. . . . .high-level .abstract .statement, .system
.constraint
Software .Management .is... .- .correct .answer. . . . .• .A .systematic .approach .to .eliciting,
.organizing, .and .documenting .the .requirements .of .the .system, .and .a .process .that
.establishes .and .maintains .agreement .between .the .customer .and .the .project .team .on .the
.changing .requirement .of .the .system.
Types .of .requirement .- .correct .answer. . . . .• .User .requirements
• .System .requirements
Stakeholders .in .the .Mentcare .system .- .correct .answer. . . . .• .Patients .whose .information .is
.recorded .in .the .system.
• .Doctors .who .are .responsible .for .assessing .and .treating .patients.
• .Nurses .who .coordinate .the .consultations .with .doctors .and .administer .some .treatments.
• .Medical .receptionists .who .manage .patients' .appointments.
• .IT .staff .who .are .responsible .for .installing .and .maintaining .the .system.
, Agile .methods .and .requirements .- .correct .answer. . . . .• .Many .agile .methods .argue .that
.producing .detailed .system .requirements .is .a .waste .of .time .as .requirements .change .so
.quickly.
• .The .requirements .document .is .therefore .always .out .of .date.
• .Agile .methods .usually .use .incremental .requirements .engineering .and .may .express
.requirements .as .'user .stories' .(discussed .in .Chapter .3).
• .This .is .practical .for .business .systems .but .problematic .for .systems .that .require .pre-
delivery .analysis .(e.g. .critical .systems) .or .systems .developed .by .several .teams.
Functional .requirements .- .correct .answer. . . . .- .Statements .of .services .the .system .should
.provide, .how .the .system .should .react .to .particular .inputs .and .how .the .system .should
.behave .in .particular .situations.
Non-functional .requirements .- .correct .answer. . . . .- .constraints .on .the .services .or .functions
.offered .by .the .system .such .as .timing .constraints, .constraints .on .the .development
.process, .standards, .etc.
Domain .requirements .- .correct .answer. . . . .- .Requirements .that .come .from .the .application
.domain .of .the .system .and .that .reflect .characteristics .of .that .domain.
Functional .requirements .- .correct .answer. . . . .• .Describe .functionality .or .system .services.
• .Depend .on .the .type .of .software, .expected .users .and .the .type .of .system .where .the
.software .is .used.
• .Functional .user .requirements .may .be .high- .level .statements .of .what .the .system .should
.do
• .Functional .system .requirements .should .describe .the .system .services .in .detail.
functional .requirements .examples .- .correct .answer. . . . .- .E.g. .mapping .of .inputs .to .outputs
- .E.g. .control .sequencing
- .E.g. .timing .of .functions
- .E.g. .handling .of .exceptional .situations
- .E.g. .formats .of .input .and .output .data .(and .stored
data?)
- .E.g. .real .world .entities .and .relationships .modeled .by .the .system
- .Add .Participant
• ."The .software .shall .display .an .option .to .add .a .participant" .- .Summon .Operator
• ."The .software .shall .summon .the .operator .if .the .participant .clicks .the .Operator .Help .icon.
A .Functional .Requirement... .- .correct .answer. . . . .- .is .a .statement .of .what .a .system .must .do
.(#1) .- .is .measured .in ."yes" .or ."no" .terms
- .usually .employs .the .word ."shall"
The .LIBSYS .system .- .correct .answer. . . . .• .A .library .system .that .provides .a .single .interface
.to .a .number .of .databases .of .articles .in .different .libraries.
• .Users .can .search .for, .download .and .print .these .articles .for .personal .study.
