Kansas State University Purchasing Contracts Management System

(KSU – PCMS)

Presentation 1 Date : 14th October 2010

ByArthi Subramanian

CIS 895 – MSE Project

Presentation OutlineProject Overview

•Motivation

•Goals

•System Overview

•Data Flow diagram

Project Modules

•Administrator Module

•User Module

•Use Case Diagrams

Project Schedule

Cost Estimation

Software Quality Assurance Plan

Prototype Demonstration

Questions/Comments

Project OverviewMotivation

Solution for helping departments at Kansas State University locate the

most appropriate options for any given contract-based purchase.

Goals

• Provide more secure and functional alternative to existing system.

• Ease of data entry and data retrieval.

• Make searchable Kansas state university contracts.

• Avoid human errors while entering contract details.

Project OverviewSystem Overview

Dataflow Diagram

Project ModulesAdmin Module

Definition:Administrator : Procurement Officer

Interacts with the system through a webpage.

Roles: Logs in to the system. Inserts contract details. Searches for contracts before performing edit. Edits existing contract details.

Project ModulesEnd-user Module

Definition:Users : University officials and employees who purchase services, supplies or equipment. Facilities, human resources, telecom department officials.

Interacts with the system through a webpage

Roles:

User RoleUniversity officials,

employeesSearch for the contract

details.

Facilities, human resources, telecom

department

Search for contracts that requires the respective departments approval.

Use Case Diagram

Current System

End user Search page

Expected Output

Application RequirementsAR1 : User Interactive graphical user interfaceAR2 : Authenticate valid procurement officerAR3 : Search based on – Contract number, contract title, vendor, Procurement officer, keywordAR4 : Search by keyword must search across contract number, contract title, vendor, procurement officer, commentsAR5 : Results must include details such as departments whose pre-approval is required.AR6 : Contract files (master contract document) must be made accessible through Kansas department of administration.AR7 : All contracts must be displayed when requested to do so.AR8 : For any unmatched search fields, a message with possible suggestions must be displayed.AR9 : If a contract with expiration date lesser than or equal to start date is entered

by the procurement officer, a message must be displayed and further data entry must not be allowed until corrected. AR10 : Search results can be sorted in ascending/descending order.

Project Schedule• Key Dates

• Presentation 1 • Date : 14th October 2010• End user search functionality.

• Presentation 2• Date : 3rd week of November 2010• Administrator screens, user screens

• Presentation 3: • Date : 3rd week of December 2010• AJAX functionalities, set up on server

Project Schedule

Cost Estimation COCOMO II is used to estimate the duration and cost involved in development of a system.

Considers factors such as reliability, software development complexity, memoryUsage etc.

2.45 * EAF * (KSLOC) ^1.09Time = 2.5 * (Effort) ^ 0.38

Effort = Number of person months (PM)Time = Duration time in months for projectKSLOC = Estimated number of source lines of code for the project (in thousands)EAF = Effort Adjustment Factor

Effort = 2.45*0.523*(1.8)^1.09 = 2.43 man-monthsTime = 2.5 * (2.43) ^ 0.38 = 3.5 months

Phase 2 deliverables

Vision Plan 2.0

Project Plan 2.0

Architectural Design Document

Software Test Plan 1.0

Technical Inspection List

Presentation 2

Prototype 2.0 Source Code

• Administrator module, interaction with the user module

Prototype Demonstration

Questions

Comments