INFO8000 - Coggle Diagram
What is systems analysis?
What are functional and non functional requirements? How do you figure them out?
Operational - The physical and technial environments in which the system will operate
Perfomance - The speed, capacity, and reliability of the system
Security - Who has authorized access to the system under what circumstances
Cultural and political - Cultural, political factors and legal requirements that affect the system
“itys” - Usability, Reliability, Availability, Serviceability, Scalability, Accessibility, Integrity, Interoperability, Capacity, Etc.
Transactions + corrections, adjustments, and cancellations
Authentication and Authorization levels
Historical data and archiving
Compliance, legal, or regulatory requirements
Structural, Algorithms, Database, Power, Network, Infrastructure, Backup and recovery
How do you define requirements?
Business Process Automation (BPA) - leaves the basic way the organization operates unchanged and uses computer technology to do some of the work
Business Process Improvement (BPI) - makes moderate changes to the way the organization operates in order to take advantage of new opportunities offered by technology or to copy what competitors are doing
Business Process Reengineering (BPR) - means changing the fundamental way the organization operates, obliterating the current way of doing business and making major changes to take advantage of new ideas and new technology.
Those activities that enable a person to understand and specify what an information system should accomplish
What is System Design?
Those activities that enable a person to define and describe in detail the system that solves the need
How do identify use cases?
Use case— an activity that the system performs, usually in response to a request by a user
Analysts decompose the system into a set of use cases (functional decomposition)
Two techniques for Identifying use cases
User goal technique
This technique is the most common in industry, Simple and effective
Identify all of the potential categories of users of the system
Interview and ask them to describe the tasks the computer can help them with
Probe further to refine the tasks into specific user goals, “I need to Ship items, Track a shipment, Create a return”
Event decomposition technique
Name each use case using Verb-Noun
Use cases define functional requirements
What is information system?
A set of interrelated components that collects, processes, stores, and provides as output the information needed to complete business tasks
Broader in scope than “app”
Includes database and related manual processes
What is Computer application (app)?
A computer software program that executes on a computing device to carry out a specific set of functions
When to use waterfall vs. Agile?
Fast on feet; responsive to change
Agile development – an information system development process that emphasizes flexibility to anticipate new requirements during development
Complete small part of system (mini-project), then repeat processes to refine and add more, then repeat to refine and add more, until done
Iterative development -- an approach to system development in which the system is “grown” piece by piece through multiple iterations
What are stakeholders and why analysze them?
Categories of Stakeholders - Users, Sponsors, Developers, Authorities, Customers
The problem of XXX - Affects XXX - The impact of which is XXX - And can be resolved with a solution which XXX
What are events? What type of events are there? Why are they important?
Event– something that occurs at a specific time and place, can be described, and should be remembered by the system
Types of Events
External Event - an event that occurs outside the system, usually initiated by an external agent or actor
Temporal Event - an event that occurs as a result of reaching a point in time
State Event - an event that occurs when something happens inside the system that triggers some process;
reorder point is reached for the inventory item
How to create a proper Use Case Diagram?
Use case diagram — a UML model used to graphically show uses cases and their relationships to actors
Actor is the UML name for a end user
Automation boundary— the boundary between the computerized portion of the application and the users who operate the application
Relationships in Use Case Diagrams
Use Case Diagrams: Steps
Identify all the stakeholders and users who would benefit by seeing a use case diagram
Determine what each stakeholder or user needs to review in a use case diagram: each subsystem, for each type of user, for use cases that are of interest
For each potential communication need, select the use cases and actors to show and draw the use case diagram. There are many software packages that can be used to draw use case diagrams
Carefully name each use case diagram and then note how and when the diagram should be used to review use cases with stakeholders and users
What is a class diagram? How do you properly create one?
A UML diagram that shows classes with attributes and associations (plus methods if it models software classes)
Describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.
Understanding Analysis vs Design
System Analysis - What is required for the new system to solve the problem
System Design - How system will operate to solve the problem
What are the lifecycle stages in System Analysis?
The process consisting of all activities required to build, launch, and maintain an information system. Six core processes are:
Identify the problem or need and obtain approval
Plan and monitor the project
Discover and understand the details of the problem or need
Design the system components that solve the problem
Build, test, and integrate system components
Complete system tests and then deploy the solution
What is an activity diagram?
Activity Diagram – describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Useful for showing a graphical model of a workflow
A UML diagram
What is a user story?
A User Story is a one-sentence description of a work-related task done by a user to achieve some goal or result
Acceptance Criteria identify the features that must be present at the completion of the task
The template for a user story description is:
“As a <role> I want to <goal> so that <benefit>"
What is UML? Why do we use it?
UML is Unified Modeling Language, the standard for diagrams and terminology for developing information systems
How do you identify classes?
Identify Domain Classes
Identify Noun -
Person, place thing
Unique/ in scope?