Академический Документы
Профессиональный Документы
Культура Документы
UML Use Case Diagrams. Use case diagrams are usually referred to as
behavior diagrams used to describe a set of actions (use cases) that some system
or systems (subject) should or can perform in collaboration with one or more
external users of the system (actors).
static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships
among objects.
Used for
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering
Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.
Following are the main usages of activity diagram:
Modeling work flow by using activities.
Modeling business requirements.
High level understanding of the system's functionalities.
Investigate business requirements at a later stage.
What new information is provided in a design class diagram (more than a
class diagram)?
Includes View Layer Classes
Domain Layer Classes
And methods
What is the purpose of user acceptance testing?
User acceptance testing (UAT) is the last phase of the software testing process.
During UAT, actual software users test the software to make sure it can handle
required tasks in real-world scenarios, according to specifications.
Chapter 2
Systems analysis five activities
Gather detailed information
Data from future users, current users, and previous users
Information from people whove built/worked on similar systems
Study existing systemsiv.Data on how the system should work and what other
systems it will interact/in-terface withb.
Define requirements
Gather information from users and documents
Create mock-ups, models, demos, and previews of how the system should look
according to the requirements.
Prioritize requirements
Establish which requirements are crucial for the system
Categorize requirements based on need, function, and importanced.
Develop user-interface dialogs
Use proto-types, models and mockups to evaluate what is best for the user andwhat
the client wants.
Evaluate requirements with users
After the above four, run everything through with the user/client to evaluate
andensure everything is what the client wants
What
Chapter 3
What is a use case?
A use case is an activity that the system performs as a result of some event or
action by a user
What are the two techniques used to identify use cases?
User goal technique and the event decomposition technique
Describe the user goal technique for identifying use cases.
The user goal technique is done by interviewing a user (or user role) to see what
their work goals or objectives are. These are low level objectives to accomplish a
piece of work or to complete a work procedure. The system then must have use
cases to support each user goal.
Describe the event decomposition technique for identifying use cases.
Look at all of the business processes that result in some type of business event. The
business events are triggers that require system processing, e.g. that require use
cases.
Why is the event decomposition technique considered more
comprehensive than the user goal technique?
Event decomposition not only looks at user initiated events (the same as the user
goal technique), but it also considers temporal events and state events. Hence it is
more comprehensive.
What is an event?
Something that occurs at a specific time and place. It can be identified, and for
purposes of systems analysis, the system must recognize it and capture some
information from it or about it
What are the three types of events?
External eventusually from a user
Temporal eventoccurs at a point in time, or due to a time interval
State eventa change of state or condition of some data within the system
Define an external event and then give an example that applies to a
checking account system.
An external event is something that occurs external to the system, and is trigger by
a user action. An example might be that a user makes a direct deposit to his/her
account.
Define a temporal event and then give an example that applies to a
checking account system.
A temporal event is one that occurs at a point in time. An example might be that at
the end of the month interest (or monthly checking account fee) is calculated and
credited to the account
What are the four operations that make up the CRUD acronym?
C = Create
R = Read or Report (output)
U = Update
D = Delete
What is a brief use case description?
A one or two sentence description of the use case and what it accomplishes.
Chapter 4
What is the problem domain?
According to the book, the problem domain is the specific area (domain) of the
user(client)s business need that is within the scope of the new system, but I really
dont like the way the book defines problem domain. Its too vague and it seems like
the writer wants to skip over it and get straight to the examples and brainstorming
techniques. So, from some research on my own, I have formed my own definition.
From my research, I define the problem domain as the area/problem that is to
beaffected/solved by the system. Specifically for SA&D, the general issue/problem
the new system is meant to solve for the client i.e. a package delivery system that
includes a website (for orders), a database (for records of payments, clients,
employees, etc.), a label generator(for the packages), and scheduling software(for
delivery and/or employee work schedules)
What is a thing called in models used by traditional analysts and
database analysts?
The thing is called a data entities by traditional analysts and database analysts.
What are two techniques for identifying things in the problem domain?
The two techniques for identifying things in problem domain shown in the book are
brainstorming technique and noun technique
Explain why identifying nouns helps identify things in the problem
domain?
Nouns are always things. So finding all the nouns will find all the things (and
more, so it needs to be refined).
What is an association, and what system development standard defines it?
An association is a relationship between things in the problem domain. It is the term
used by UML
What is multiplicity, and what is the other term used by traditional
analysts and database analysts?
It is a measure of the number of links in an association between an object in one
class and the objects in another class. In traditional analysis it is called cardinality.
Systems Analysis and Design in a Changing World, sixth edition
What is the minimum multiplicity for the association that reads a customer
places zero or more orders? Zero
What is the maximum multiplicity for the association that reads an order
is placed by exactly one customer? One
In UML, what are three types of relationships found on a class diagram?
Three types of relationships found on a class diagram are
generalization/specialization, whole-part, and association
Chapter 5
What two UML diagrams are used to model domain classes?
Problem domain class diagram and state machine diagram
What is the purpose of an SSD?
What symbols are used in an SSD? An SSD (system sequence diagram) is used to
describe the messages that flow into and out of a system, i.e. between the system
and the use case user. The symbols include: Stick figure for the actor Box with
object name for the system object Vertical dashed lines for object lifelines
Horizontal arrows for messages Horizontal dashed arrows for return data
Comment box for comments
Chapter 6
What is the primary objective of systems design?
The objective of systems design is to define, organize, and structure the
components of the finalsolution system that will serve as the blueprint for
construction.
What is the difference between systems analysis and systems design?
The objective of systems analysis is to understand the needs and requirements,
while theobjective of design is to figure out the solution to those needs and
requirements.Analysis is tounderstand the problem, design is to solve the problem.
(and implementation is to build thesolution.)