Outcome 2 Flashcards
Data Collection Methods
- Survey
- Report
- Interview
- Observation
Functional Requirements
What the solution will do
Non-Functional Requirements
other requirements the client would like the solution to have, that doesn’t effect what the solution will do
Non-Functional Requirements - Components
Usability
Portability
Reliability
Robustness
Maintainability
Scope
Describes what the solution will and wont do
Constraints
Anything that may limit the options for development or delivery
Types of Constraints
Economic - includes time and cost
Legal - when legislation restricts the solution from performing certain activates
Social - limitations of people to perform functions
Technical - related to hardware and software available to the project
Usability - things like screen size, complexity of the solution
SRS
Software Requirements Specification
SRS - Features
Constraints
Scope
Functional & Non Functional Requirements
Optional - appendix containing other information needed to interpret the requirements (OS, third party tools required)
SRS - Purpose
- to ensure that the clients problem or opportunity is understood
- to form the basis of the design
- to be used as the basis of the evaluation criteria
Organizational Goals
Defines an organizations purpose, assist its growth and help is achieve financial objectives
Organizational Objectives
Specific, measurable, achievable steps towards achieving a larger goal
quantifiable - can be proved to be achieved with stats, observations and logs
Organizational Goals - Official
goals an organization aims to achieve
Organizational Goals - Operative
goals that are necessary to achieve an outcome
Use Case Diagrams (+ Actor + Use Case Definitions)
Describes how a user will interact with a solution - Created using UML (unified modelling language)
Actor - entity that can interact with the solution
Use case - a function or transaction an actor can use
Use Case Diagrams - Extend
means the entirety of a different use case MAY be included in another
Use Case Diagrams - Include
means the entirety of a different use case is USED in the running of another
Use Case Diagrams - System Boundary
drawn with a rectangle that demonstrates whats included in the solution
Context Diagrams
Visualization of a system that indicates data flow in and out of a solution
Context Diagrams - Process
Abstract representation of the whole system
Represented as a circle
Context Diagrams - Entity
Users or external systems that interact with the system
Represented as a rectangle
Context Diagram - Data Flow
Represents a single piece of data or a logical connection of data as it moves in or out of a system
Represented as an arrow with a label on top
Data Flow Diagrams
Graphical visualisation of the flow of information in and out of a solution
Contains the core processes in the solution
Data Flow Diagrams - Processes
abstract representation of a function (e.g. validate PIN).
Must start with a verb
represented as a circle
Data Flow Diagrams - Entity
users or external systems that interact with the processes
represented as a rectangle
Data Flow Diagrams - Data Flow
represents a single piece or logical collection of data as it moves between processes
represented as a line
Data Flow Diagram - Data Store
represents a collection of data in a solution.
Represented by two parallel lines, with the name of the data in store between them
Techniques for Generating Design Ideas
Brainstorming
Consulting end users
Mindmapping
Factors influencing the design of solutions x5
- Usability
- Affordance
- Security
- Interoperability
- Marketability
User Experience
Design that provides relevant and meaningful experiences for users.
Includes things like hierarchy, navigation and functionality
User Interface
Focuses on appearance. Includes things like colour, shape, spacing and the look and feel of the solution
Gantt Chart - Milestones
The achievement of a significant stage in a project
time length is 0
Represented with a diamond on the gantt chart
Gantt Chart - Dependencies
tasks that require another task to be finished before the task can be completed
arrows used to indicate dependencies
Gantt Chart - Critical Path
Sequence of tasks from beginning to end.
Contains no slack time, is the longest duration and is the minimum possible time the task can be completed
