PASSING THE WORD BY FRANKLYN OMORUAN. Written specifications Manual is the external specification of the product Manual is the external specification.

Slides:



Advertisements
Similar presentations
Robert Lockyer.
Advertisements

Software Requirements
Project management Project manager must;
1 SWE 513: Software Engineering Requirements II. 2 Details in Requirements Requirements must be specific Examples -- university admissions system Requests.
Trusted Hardware: Can it be Trustworthy? Design Automation Conference 5 June 2007 Karl Levitt National Science Foundation Cynthia E. Irvine Naval Postgraduate.
Software Engineering COMP 201
1 presented by: Tim Haithcoat University of Missouri Columbia QA/QC and Risk Management.
1 / 26 CS 425/625 Software Engineering Software Requirements Based on Chapter 5 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6 th Ed.,
Software Requirements
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
Software Requirements
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
Software Configuration Management (SCM)
1 Software Requirements Specification Lecture 14.
© Copyright 2011 John Wiley & Sons, Inc.
Software Engineering Chapter 6 Software requirements
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
Supporting Information Needs by Ostensive Definition in an Adaptive Information Space Iain Campbell 1995 Gretchen Schwarz.
7M822 Software Requirements Introduction 7 September 2010.
Course Instructor: Aisha Azeem
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Presented by Collin Kanaley.  The manual is a necessary tool, but not a sufficient one.  The manual is the chief product of the architect.  It should.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Welcome to OBJECT ORIENTED PROGRAMMIN Date: 10/09/2014 Prepared By Prepared By : VINAY ALEXANDER PGT(CS) KV jhagrakhand.
Chapter 4 – Requirements Engineering
Planning for the Solution
RUP Implementation and Testing
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements.
Designing a DSL for Information Systems Architecture
©Ian Sommerville Software Engineering Slide 1 Software Requirements l Definition: Description and Specifications of a system l Topics covered: Functional.
Adaptive Processes © Adaptive Processes Simpler, Faster, Better Software Requirements.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
Software Requirements Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn Lecture 4 & 5.
Lesson 3 McManus COP  You have to tell them ◦ what to do ◦ what to use ◦ in what order to do itand ◦ what to do if your user does not do what.
1 Some initial Design suggestions… Getting started… where to begin? Find out whether your design architecture will work… as soon as possible. If you need.
The Six Basic Principles The Constitution. Terms Limited government Constitutionalism Rule of law Federalism Elastic clause Separation of powers Checks.
Requirements Engineering Overview Senior Design Don Evans.
1. 2 Preface In the time since the 1986 edition of this book, the world of compiler design has changed significantly 3.
CS 460/660 Compiler Construction. Class 01 2 Why Study Compilers? Compilers are important – –Responsible for many aspects of system performance Compilers.
L To identify the services that the customer requires from a system and the constraints under which it operates and is developed.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
Review of Parnas’ Criteria for Decomposing Systems into Modules Zheng Wang, Yuan Zhang Michigan State University 04/19/2002.
Software Engineering Chapter 6 Software requirements Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
Software Requirements Specification Document (SRS)
Requirements Analysis
Formal definitions written in the manual.  Written specification  External product of the Architect  Details what the user sees  Does not detail what.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Overview of Compilation Prepared by Manuel E. Bermúdez, Ph.D. Associate Professor University of Florida Programming Language Principles Lecture 2.
Welcome to OBJECT ORIENTED PROGRAMMING Prepared By Prepared By : VINAY ALEXANDER PGT(CS) KV jhagrakhand.
1 Software Requirements Descriptions and specifications of a system.
Agile Requirements Introducing User Stories. Key Principles for Agile Requirements Active user involvement is imperative Agile teams must be empowered.
Advanced Computer Systems
Software Testing.
Introduction to Compiler Construction
Software Requirements
Software Verification and Validation
Software Configuration Management
Software Requirements
Programming Languages
Lecture 09:Software Testing
An Introduction to Software Architecture
Requirements Document
Chapter 5 Architectural Design.
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Software Requirements
Presentation transcript:

PASSING THE WORD BY FRANKLYN OMORUAN

Written specifications Manual is the external specification of the product Manual is the external specification of the product Prescribes and describes every detail Prescribes and describes every detail But not everything is described including interface But not everything is described including interface Also refrain what the user does not see Also refrain what the user does not see Finest piece of manual is Gerry Blaauw’s appendix system 360 Finest piece of manual is Gerry Blaauw’s appendix system 360

Written specifications contd. Describes care and precision Describes care and precision Limits of system/360 compatibility Limits of system/360 compatibility must show an implementation for any feature but not attempt to dictate it. must show an implementation for any feature but not attempt to dictate it.

Formal Definition Manual writer must strain himself and his language to achieve precision needed Manual writer must strain himself and his language to achieve precision needed Precision is the stock in trade Precision is the stock in trade Has merits and demerits Has merits and demerits Merits are formal definition are precise, complete and can show structured principles. Merits are formal definition are precise, complete and can show structured principles.

Demerits The implementations may be over-prescribed even the externals The implementations may be over-prescribed even the externals Use of implementation as a formal definition is susceptible to confusion Use of implementation as a formal definition is susceptible to confusion Must refrain from modification to the implementation while it is serving a standard Must refrain from modification to the implementation while it is serving a standard

Direct incorporation Technique for disseminating and enforcing definition is available for software architect Technique for disseminating and enforcing definition is available for software architect Useful for establishing syntax if not semantics of intermodule interfaces Useful for establishing syntax if not semantics of intermodule interfaces Whole interface is referenced only by symbolic names, declaration can be changed by adding new varables with only recompilations Whole interface is referenced only by symbolic names, declaration can be changed by adding new varables with only recompilations

Conferences and Courts Two levels of meeting Two levels of meeting Conference of all architects plus official representation Conference of all architects plus official representation Chief system architect presides Chief system architect presides Emphasis on creativity rather that mere decision Emphasis on creativity rather that mere decision

Multiple Implemanetation System/360 had two important advantages System/360 had two important advantages Enough time to work carefully and political clout Enough time to work carefully and political clout Most computer projects there are time machine and manual do not agree Most computer projects there are time machine and manual do not agree

Telephone Log No matter the precise specification many architectural interpretation question rises No matter the precise specification many architectural interpretation question rises Are kept by architect, it records questions and every answer Are kept by architect, it records questions and every answer It is informal but quick and comprehensive It is informal but quick and comprehensive

Product Test Daily adversary is the project manager best friend. Daily adversary is the project manager best friend. Checks machine and programs against specification Checks machine and programs against specification Pinpoints every conceivable defect and discrepancies. Pinpoints every conceivable defect and discrepancies.

summary What the chief architect produces are written specifications for the system in the form of the manual. What the chief architect produces are written specifications for the system in the form of the manual. It should describe the external specifications of the system in detail, i.e., everything that the user sees. It should describe the external specifications of the system in detail, i.e., everything that the user sees. The manual should be altered as feedback comes in from the implementation teams and the users. The manual should be altered as feedback comes in from the implementation teams and the users.