By: Muhammad Raza Ali Khan

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House Mark Parker (800)
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Software Life Cycles ECE 417/617: Elements of Software Engineering
SYSC System Analysis and Design
Rational Unified Process
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
1 SOFTWARE LIFE-CYCLES Beyond the Waterfall. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
1 SWE Introduction to Software Engineering Lecture 5.
Iterative development and The Unified process
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
The web application development process Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 1.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
S/W Project Management
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
The Rational Unified Process
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Rational Unified Process (Part 1) CS3300 Fall 2015.
Rational Unified Process Fundamentals Module 4: Disciplines II.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Identify steps for understanding and solving the
Object Oriented Design and Analysis Rational Unified Process.
Rational Unified Process , Introduction to UML. What is RUP? The Rational Unified Model is a software engineering process Both process and product Provides.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Foundations of Geospatial System Development II Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute.
{ Phases of Project & life cycle Prepared by: Syed ShahRukh Haider.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
The Rational Unified Process 1 EECS810: Software Engineering.
The principles of an object oriented software development process Week 04 1.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
1 Process activities. 2 Software specification Software design and implementation Software validation Software evolution.
June 2008Mike Woodard Rational Unified Process Overview Mike Woodard.
Software Development Framework
Iterative development and The Unified process
The Web Application Development Process Models
Introduction to Software Engineering
Object Oriented Analysis and Design
Rational Unified Process
Rational Unified Process (RUP)
Chapter 2 – Software Processes
Software engineering -1
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Presentation transcript:

[Project Scope Management] Requirement Specification Document for Purchase Management System By: Muhammad Raza Ali Khan Information Systems and Technology Division, Securities and Exchange Commission of Pakistan

Presentation Outline Software Process Life Cycle adopted by SECP SECP Projects Overview Problems In Existing System What is RSD? What RSD Covers? secPurchase WorkFlow Procedures Future secPurchase WorkFlow Procedures HQ and CRO Communication Suggested Sample Reports

Optimized Process Lifecycle Rational Unified Process (RUP): Rational Unified Process is a flexible software development process platform that delivers customized yet consistent process guidance to project teams helping them during different phases i.e. analysis to implementation. The Optimized Process Lifecycle (OPL): OPL name is given to the standard software process lifecycle and adopted by SECP for all its software projects. OPL is based on the RUP standard. OPL Phases and Iterations OPL Workflows RUP: Rational Unified Process is a flexible software development process platform that delivers customized yet consistent process guidance to project teams helping them during different phases i.e. analysis to implementation.

SEC’s Software Process Life Cycle:OPL Workflow Sequence o activities that eventuates into a productive result. Phase Multiple iterations in the optimized process lifecycle Iteration Complete iteration results in a S/w product Dimensions: 1. Horizontal dimension Represents time and dynamic aspect of the process 2. Vertical Dimension Static aspects of the process i.e. workflows

SEC’s Software Process Life Cycle:OPL Phases: OPL has four phases Inception Elaboration Construction Transition Each phase is concluded with a milestone and certain deliverables

SEC’s Software Process Life Cycle:OPL

SEC’s Software Process Life Cycle:OPL INCEPTION PHASE: Establish the feasibility: Define the Scope Initial requirement capture Initial risk analysis Cost benefit analysis Initial Use Case model Milestone :Lifecycle Objectives: Stakeholders concurrence on the Scope definition Requirements understanding based on use cases Deliverables: Requirement Specification Document Risk Analysis Report Project timeline sheet

Graphical Presentation (Inception) SEC’s Software Process Life Cycle:OPL Graphical Presentation (Inception) Establish the feasibility Initial Use case model Risk identification Define project Scope

SEC’s Software Process Life Cycle:OPL ELABORATION PHASE: Understand the Problem: Domain Model Architecture document Use case analysis Risk Assessment plan revised Milestone :Lifecycle Architecture: Detailed system objectives and scope Resolution of major risks Deliverables: Story board Report Specification Document Design Document Table

Graphical Presentation (elaboration) SEC’s Software Process Life Cycle:OPL Graphical Presentation (elaboration) Understand the problem Build the architecture Components Packages

SEC’s Software Process Life Cycle:OPL CONSTRUCTION PHASE: Understand and built the solution: Depth of implementation (stubs are fleshed out) Implementation of all details Analysis continues but coding and design predominate Milestone : Initiate Operational Capability: Check if the product release is stable and mature enough to be implemented Check if stake holders are ready for transition to the end users Compare the actual expenditure with planned expenditure (check if they are acceptable or not) Deliverables: Releases Help files User manuals

Incrementally build the system SEC’s Software Process Life Cycle:OPL Understand and build the solution Incrementally build the system Analysis Project Management Design Change Management Implementation

SEC’s Software Process Life Cycle:OPL TRANSITION PHASE: Roll out the solution: Transition the system to the user community Customer Acceptance tests Finalize Documentation User manuals, installation guid Milestone : Product Released: Is the user satisfied? Compare the actual expenditure with planned expenditure (check if they are acceptable or not) Deliverables: Test plans. Installation programs.

Graphical Presentation (transition) SEC’s Software Process Life Cycle:OPL Graphical Presentation (transition) Roll out the solution Users manuals, installation guide Transition system to users Software testing

Reports Specification Document SEC’s Software Process Life Cycle:OPL Software Process Life Cycle Analysis Design Client Interaction Development QA Deployment Analysis Deliverables SWPLC/OPL: A systematic means for decomposing and capturing process knowledge into well-defined (typed) process-definition elements, such as role, artifact, activity, guidelines, concepts, and so on. A set of rules and policies to assemble and organize these elements into a cohesive customized process. An extensible process template to serve as a basis for process authoring. Initial Test Plan Feasibility Report Project Plan RSD Reports Specification Document Supporting Workflows Project management,Change management etc Storyboard

SECP’s PMS Project Overview: Manual System View: Computerize System View: Purchase Management System (PMS) Inventory Management System (IMS) Financial Management System (FMS)

Problems In Existing System Maintaining multiple documents for same data Risk of inconsistency among documents Synchronizing multiple documents in case of change is difficult More chances of mistakes Referring to Past Data is Difficult

Problems In Existing System Customized Reports are Difficult to Produce As the amounted Overspent under the head of stationary is 0.205 million. Only a Few Reports Sent to HQ Monthly Annually Higher level information

What is RSD? Establishes a common understanding among the project stakeholders Tracks and avoids loss of the requirements Provides a clear statement of requirements Organized requirements helps trace requirements evolution throughout the development life cycle and into the maintenance phase. Reduces project cost overruns and schedule delays Detect requirement errors, which avoids unnecessary cost associated with implementing the wrong requirements.

Financial Management System Inventory Management System What RSD Covers? Assumptions Interfaces Users Constraints Processes H/w S/w Technology Performance Environment Use Cases Characteristics Responsibilities Requirement Specification Document Financial Management System Inventory Management System

secPurchase WorkFlow Procedures Capital Purchase Requisition Tender Management Quotation General Comparative Statement Purchase Order Supplier Management Petty Cash Advance Statement Signatory Management Purchase Requisition Cash Cash Purchase Statement User Management

Outsource Service Management Future secPurchase WorkFlow Procedures Outsourcing of Admin Services Outsource Service Outsource Service Management Service Proposal Contract Managed Supplier Purchase Order secInventory

Company Registration Office HQ and CRO Communication WAN Information Flow Company Registration Office Headquarter

Suggested Sample Reports Purchase Requisition/Pending Purchase Requisition Purchase Requisition Listing Quotation Quotation Listing Comparative Statement Purchase Order/ Pending Purchase Order (Goods & bills not yet received) Capital Expenditure Proposal Form Report Petty Cash Advance Statement Cash Purchase Statement

We the Information systems and Technology Division, makes the Commission's dreams a reality