exam2 cis 3300

Specify a Use Case Diagram

Used to provide an overview of all or part of usage requirements

Communicate the scope of a developing project

• Specify a use case

narrative document that describes the sequence of events of an actor using a system to complete a process

• What is "Traceability"?

Link between use cases and goals. How they correlate. Link two requirements to each other. Help manage change

• What is IKIWISI?

I'll know it when I see it

• What's a prototype?

A preliminary model of something

• Define a horizontal prototype

. A prototype that focuses on the different features of a system

• Define a vertical prototype

A prototype that focuses on the functionality of a system

• What is level of fidelity of a prototype?

it is the level of detail; high versus

• What are the elements of a business process model?

Who - the actor or swim-lane indicators the active agent

• -typically human or business unit 0

• Action - the task or process

• Sequencing - simple ordering; parallel flow; choice; merge or rejoin flows

• Advanced details - synchronized events and default choices

• Specify qualities and constraints

• Constraints - a restriction forced on the choices of developers while designing and constructing a product

• Qualities- a non functional requirement that needs service or to be fixed characteristic of a product

• Be able to use a list of common non-functional system requirements to specify quality goals for a specific project (Alexander, p. 137)

o Goals which are satisfied to varied degrees dependent on the option selected (i.e., min/max goals)

o Qualities and constraints (known together as non-functional requirements or NFRs) show that you know how people expect the system to be, rather than what they want it to do.These are critically important requirements.

o Qualities such as safety, performance, reliability, usability and durability govern consumers' product choices and company reputation

• Describe three techniques to prioritize requirements

• In or out - if it is in then release if it out, hold for future

• Pairwise comparison and rank ordering- for each requirement, compare it to all other requirements. N-1

• Moscow- shows as:Must,should could and won't, pretty much 3,2,1,0 priority

• Dollar allocation- stakeholders can give their money to the requirements they care for

• Value/Cost- are assigned requirement (sometimes Risky), select those high in value with low cost and low risk

• What's a trace link among development artifacts?

• A link that is associated two or more development artifacts in a relationship, like it depends on, or derived from, or satisfies

• What's a trace suspect? If a goal changes, check if the linked use case needs to change too

• When the goal or link has been changed without updating the other.

• How are use case statements, use cases, and goals related via trace links?

• Goals trace forward to use cases and use cases trace forward to code

How is a release plan (of selected requirements) used to manage the incremental release of software?

• It selects requirements to be implemented in the next release

• What are two ways to mitigate requirements leaks (uncontrolled requirements inclusions that increase scope)? Reduce access to requirements document, have a final approval group for requirements

• Every requirement must be approved by some person

• Control Access.

• What are the advantages of interviewing?

• ADVANTAGES - 1. Engaging with stakeholders. Give personal attention, show they are being heard, what they say is being heard, requirements turn into product and services. 2. Dialogue and feedback. 3. Follow up. Second interview - fill up any gaps. Ask new questions and suggestions.

and disadvantages of interviewing

• DISADVANTAGES - Only what they know people don't think outside the box. One hand clapping - only one point of view at a time. Unresolved conflicts. Stakeholders do not get to hear each others point of view.

• What are some common guidelines for interviewing?

• Introduce yourself. Be friendly and professional. Don't assume stakeholders know anything. Work in groups. Treat interviewers as experts. Listen more and speak less. Do not force your opinion. Use your interview plan as a guide

• What are the four types of models most useful in requirements interviews?

• Stakeholder maps or union models, Goal models, Rick pictures, and flowcharts or scenario pictures

• What is observation?

• Ethnography, or field work, as you leave your office to see what happens in the field.

• What is apprenticeship?

A situation in which a learner works intensively with an expert to learn how to accomplish complex tasks.

• What is the difference between the meeting and a workshop?

• Workshop is a specialized meeting structured to bring exactly the right people together to solve a problem using a planned sequence of activities. Those people maybe the stakeholders in the project, members of the development team, or external experts to assist with specific task. Meetings can be called adhoc with no planning or structure to address an immediate issue.

• Be able to define a workshop mission

• Anything on a project that needs the skill involvement of stakeholders and requirement specialist. For example: to define the goals for xyz product, to draft the performance requirements for the xyz products

• What are examples of group media for workshops?

• Be able to describe advantages and disadvantages of the following: project wall, project website, project wikis

• Project wall - (advantages) encourages more democratic approach, people can share work in progress, or list of risk and assumptions; (disadvantages) it's purely passive, it's used for discovery depends heavily on enthusiasm of team members. It cant provide the energy and focus of a workshop, and remote teams can't see it.

• Project website - (advantage) - it's invaluable for sharing standard procedures, dates and meetings and deadlines. It also is an ideal place for publishing baseline versions of project documents; (Disadvantage) - website can still feel like a read only notice board. Only a few people on the project update the website. It turns into a passive medium and it's not very effective at stimulating discovery of requirements.

• Project wikis- (Advantage) -it allows a team to create a shared structure of team pages which could describe a project requirements design, issue, and day to day decisions and so on. It allows group members to watch for changes to an item such as usability requirements page. (Disadvantage) - Wikis can sometime stir up controversies rather then facilitating agreement. The easiness of editing can encourage team members to keep editing requirements causing projects to go scope creep

• How is a user story (or use case) a boundary object? (What are the different roles that understand it?)

• They are used in workshops to help people understand the message simpler.

• They are used to communicate to clients. •

• Why are user stories and use case so popular in requirements practice?

o User story goes into details, common to agile methods

o Use cases goes into more details than user stories.

o Both is easy for anybody to understand

• What is represented left-right (sequence)?

• Left is the use case, right is the manual.

• What is an object?

An object is an instance of a class.

What is the class?

• A class is the parent or type of an object

What is the difference between an object and a class?

• The difference is that an object is a singular instance of a class

• Describe and provide an example of a class diagram (classes their attributes & operations; associations

It is a summary of classes and their relationships; they are abstracted from the underlying objects which they describe

• How can conceptual classes be found (acquired?) What is text or form analysis?

Text - analysis of natural language documents found within organization as a source of knowledge about important classes, associations, and operations

• Form - analysis of structured communications found within organization, including existing computer forms, as a source of knowledge about important classes, associations, and operations

• Describe and use UML modeling techniques, including: generalization, aggregation, composition, association classes, roles names

• Associations - one to one, zero to one, etc.

• Roles names - name that are added at the end of the association. For example, person to company has role names of employee to employer

• Aggregation - assemble a class from other classes; folder to picture; the open diamond

• Composition - contained objects are created and destroyed with the container; the filled in diamond

• Generalization - a relationship between one or more refined versions of a class; the filled in arrow; subclasses

What is a main driving goal for requirements analysis and specification? (In particular, why do we have so many notations and activities? How do they contribute to the final deliverable

The goal of requirements analysis is to accurately gather what a system is expected to do. Through effective dialog, ambiguity should be eliminated in the requirements so that all parties understand what the software will do. This minimizes any errors in the later stages of documentation and development of the software which in turn saves money. If done correctly, the final deliverable is a robust system that meets stakeholders needs

• What role does structure play in requirements analysis and specification?

Structure reduces ambiguity and facilitates analysis.

o requirements structure tells you where the specific requirements for the project can be found

• Think about the structure of the goals, UML diagrams, and the vision document

• What role does dialog play in requirements analysis and specification

o Dialog enables feedback with stakeholders which refines the requirements and reduces ambiguity. storyboard, workshops, interviews ○ agile/open source ○ reduce ambiguity