3.3.1. Types of specification: – Requirements specification – Design specification – System specification and the differences between them.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

Object-Oriented Software Engineering Visual OO Analysis and Design
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Database Software Creation Process Arvin Meyer, MCP, MVP
Chapters 7 & 9 System Scope
Chapter 4 Enterprise Modeling.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
System Design and Analysis
Info /7 DMU1 The story so far… Systems Analysis & Design Academic Year 2008/9 Lecture 10.
Systems Development Life Cycle
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Chapter 13: Designing the User Interface
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
National Diploma in Systems Analysis and Design Data Flow Modelling.
staffs.ac.uk Process Model. staffs.ac.uk Contents Provide definitions Explain the components and representations Introduce a step.
The Software Development Cycle Defining and understanding the problem.
Introduction to Systems Analysis and Design Trisha Cummings.
The Software Development Life Cycle: An Overview
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Managing the development and purchase of information systems (Part 1)
Chapter 17 Database Design Using the REA Data Model Copyright © 2012 Pearson Education 17-1.
Requirements Analysis
Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.
Data Flow Diagrams.
Phase 2: Systems Analysis
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Chapter 14 Information System Development
Feasibility Study.
OCR ICT for A2 © Hodder Education 2009 Chapter 1 The systems cycle.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
Project Life Cycles.
Approaching a Problem Where do we start? How do we proceed?
Chapter 12 Information System Development. Chapter 12 Objectives Next List the phases in the system development life cycle Identify the guidelines for.
13 Step Approach to Network Design Steps A Systems Approach 8Conduct a feasibility Study 8Prepare a plan 8Understand the current system 8Design.
Feasibility study A feasibility study is a preliminary investigation of a problem. It is used to decide whether a solution is possible and what effects.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Chapter 7 The Object-Oriented Approach to Requirements.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
based on material from Mott,Leeming,Williams Design of Solutions AQA INFO 1 Topic 3.
Project roles and responsibilities
To be completed Your proposal  Your House style  Your site plan  Page plans (a draft layout for each of your five pages)  A design mock-up -  All.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
CS523 Database Design Instructor : Somchai Thangsathityangkul You can download lecture note at Class Presence 10% Quiz 10%
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
1 Systems Analysis & Design 7 th Edition Chapter 2.
TYPES OF SPECIFICATION THIS PRESENTATION COVERS TYPES OF SPECIFICATION: REQUIREMENTS SPECIFICATION DESIGN SPECIFICATION SYSTEM SPECIFICATION AND.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
Learning Objectives Today we will Learn: The different methods of implementation The differences between user and technical documentation.
Systems Development Life Cycle
CompSci 280 S Introduction to Software Development
Systems Planning and Analysis
Gary Hughes, South Oakleigh College
Systems Analysis and Design
Chapter 11 Information System Development
Database Design Using the REA Data Model
“What do I do ?”, “How do I do it ?”, What do I do it with ?
تحليل وتصميم نظم المعلومات
A01 DESIGN To be completed Your proposal  Your House style 
Members: Keshava Shiva Sanjeeve Kareena
Types of Specification
Chapter 5 Understanding Requirements.
AICT5 – eProject Project Planning for ICT
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

3.3.1

Types of specification: – Requirements specification – Design specification – System specification and the differences between them.

Developed by the systems analyst who has completed the feasibility and analysis stages of the systems life cycle. This specification is used explain what the system is supposed to do and how it will achieve this. It should also explain how the users will interact with the software.

The contents of the requirements specification should also include: – The purpose of the system. i.e. what are it’s objectives? – Scope of the system. – The proposed timescale of the system. – End-user defined constraints including: Budget Time hardware and software choices. – A contract.

The events outside the system that cause the system to react. The actors outside the system that interact with the system. The information that flows between the system and the actors outside the system. The major functions included in the system. The user population.

Created by the system’s designer. The contents of the design specification will be different depending on what type of system is being created. – For example, a spreadsheet needs to contain designs for formulas whereas a website needs to contain information about how pages are linked. There might be some similar design aspects to take on board though… – Data input forms might need to be designed?

The contents should include: – The purpose of the system – Assumptions, limitations and constraints – Inputs and Outputs Documents and screens/interface – Error messages – Styles Colours, font sizes, house style etc – Validation rules

The contents should include: – Processing requirements/queries – Data structures – Modelling diagrams DFDs, ERDs, STDs – Hardware – Software/programming language to be used – Test plan

This specification defines the requirements of the system including: – Operational requirements: What operations should the system carry out? – Information requirements: What information should be provided to the end-users? – Volume requirements: How much processing will the system have to handle.

This specification defines the requirements of the system including: – General system requirements: Degree of data accuracy needed Security issues Need for audit trails The system’s ability to expand if the company needs to grow or handle more data.