September 3, 2013 Project on Inventory Control System (PICS) P.I.C.S - 2013.

Slides:



Advertisements
Similar presentations
QuEdge Testing Process Delivering Global Solutions.
Advertisements

Software Quality Assurance Plan
(Insert Title of Project Here) Kickoff Meeting (Month Date, Year)
<<replace with Customer Logo>>
Agile Architecture Prabhu Venkatesan for COMP-684.
Visual Studio Team System (VSTS). Richard Hundhausen Author of software development books Microsoft Regional Director Microsoft MVP (VSTS) MCT, MCSD,
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
1 presented by: Tim Haithcoat University of Missouri Columbia QA/QC and Risk Management.
Business Intelligence Dr. Mahdi Esmaeili 1. Technical Infrastructure Evaluation Hardware Network Middleware Database Management Systems Tools and Standards.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Project Documentation and its use in Testing JTALKS.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Software Configuration Management
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Software Engineering Tutorial. Tutorial objectives  Direct application for the SW engineering activities.  Discuss real software development case studies.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Final Year Project Presentation E-PM: A N O NLINE P ROJECT M ANAGER By: Pankaj Goel.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
10/7/2005 ISECON Using a “Real” Systems Development Project to Enrich a Systems Analysis and Design Course Janet Helwig Dominican University.
Project Management Process Overview
A brief overview of the project By Group 2 Barry Amir Bhumi Shubh.
A brief overview of the project By Group 2 Barry Amir Bhumi Shubh
Extreme Programming Software Development Written by Sanjay Kumar.
Database Design, Application Development, and Administration, 5 th Edition Copyright © 2011 by Michael V. Mannino All rights reserved. Chapter 2 Introduction.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software Configuration Management
Software Testing Life Cycle
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
PROJECT COSTING ZETA ERP. FLOW PANEL.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
WFO Planning Tool RFC & FCT
Identify steps for understanding and solving the
Boston University Project Management Association Website Development Group 3 Team3 CS632 Dr. Vijay Kanabar Team Members Mario Soto Emily Ziegler Kevin.
Basic of Project and Project Management Presentation.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
STUDENT ACADEMIC PLAN BY TEAM NETINFOTECH April 30, 2013.
Project Dragon Small Business Website Content Management System.
Software Quality Assurance
Project Life Cycle.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
Latifa AlAbdlkarim King Saud University October,2009.
Develop Project Charter
Agenda  Project Overview  Project Goal & Scope  Estimates  Deadline  Project Environment  Delivery Plan  Project Plan  Team Structure  Risk Analysis.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
INTRODUCTION Develop fully functional system for RSA (Recruitment Solution Agency). Job seeker can register online. Apply for jobs after registration.
Project Management.
The Project Plan Plan Your Work, then Work Your Plan
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Online School Management System Supervisor Name: Ashraful Islam Juwel Lecturer of Asian University of Bangladesh Submitted By: Bikash Chandra SutrodhorID.
T Iteration Demo LicenseChecker I2 Iteration
Work In Progress Presentation. Orders Alex Thornton.
Leveraging Technology and Process Optimization Ivan Nedovba Manager - Revenue Cycle.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Project Management Software development models & methodologies
Project Management PTM721S
Software Verification and Validation
IEEE Std 1074: Standard for Software Lifecycle
Create a project schedule
How to Successfully Implement an Agile Project
Software Development In Agile
Presentation transcript:

September 3, 2013 Project on Inventory Control System (PICS) P.I.C.S

Introduction to the Team Name Duty Contact Mohammed Abdul Jabbar Zeeshan Project Manager / Technical Head +61 Chandran Johanan Programmer / Design Architect +61 Kanwaljeetsingh Dhaliwal System Analyst / Quality Analyst +61 Kavitha PoolaRisk Manager / Database Administrator +61 P.I.C.S

Responsibilities Project manager Mohammed Abdul Jabbar Zeeshan  To distribute tasks amongst group members and record tasks allocated at the regular meetings.  To provide regular feedback to supervisors and team members.  To be available for team members to see when there is a problem within the group.  To ensure that the project keeps to the schedule. P.I.C.S

Responsibilities Programmer Chandran Johanan  Prepare programs and codes for the running the project programs.  Write the test cases earlier to avoid the errors in the programs.  Write proper program and define all codes perfectly to understand others.  Divide the task in to the programming team.  Run the program before implement it and solve the errors. P.I.C.S

Responsibilities System Analyst Kanwaljeet Singh Dhaliwal  Collect the requirements from the user or clients.  Prepare well defined specifications for all the requirements.  Analyze the system properly for the project requirements.  Check that all the requirements should be met in the project. P.I.C.S

Responsibilities Database Administrator Kavitha Poola  Collect all the data needed for the project.  Manage the database system.  Define all the entities and objects for the project.  Prepare use case diagrams, ER diagrams, network diagrams for the project.  Distribute the task in to the database team. P.I.C.S

Introduction to the client RoleNamePhone Sponsor Michael ClientJake Project SupervisorKT P.I.C.S

Introduction to the Project Project Detail:  Creating an application in order to control the inventory system of the client “ Rundle bistro bar”.  Budget: $12,000  Time: 3 months P.I.C.S

Client requirements  Dynamic inventory control management application.  Manage stock, order stock and request the stock  Add/delete product(s)  Update P.I.C.S

User requirements  Login  View Products  Add/Remove product(s)  Place Order  Generate Invoice  Update Stock  Request Stock P.I.C.S

Project Scope  Project name- Project on inventory control system (PICS)  Project Justification  Product Characteristics and Requirements  Project/Product Deliverables  Risk Management  Success Criteria  Assumptions P.I.C.S

Project Scope Project Title: Project on inventory control system (PICS)  Project Justification:  Interactive system to order, verify and request new stock.  An application for inventory management which allows user to put entries database.  Verification and validation of stock. easy access to request the stock. P.I.C.S

Project Scope Product Characteristics and Requirements:  Application with login ID at front page.  Second page, user categories selection.  Drop down list of products of category and quantity required.  Final page, item list, quantity with unique product ID.  Invoice to order required products. P.I.C.S

Project Scope Risk  Absence of team members.  Lack of communication.  Conflict with client.  System failure. P.I.C.S

Project Scope Success Criteria:  Weekly report.  Proper communication.  Kick off meetings.  Responsibility and help each other.  Contingency plan  Avoid absentism which leads to the failure. P.I.C.S

Project Deliverables SPMP WBS Status Reports Milestone Reports SRS SADD  SDD  Test Plan  Quality Assurance Plan  Risk Management Plan  Source and Object code P.I.C.S

Development Methodology Agile methodology 1.Active user involvement 2.Decisions making 3.Requirements evolve 4.Capture requirements at a high level; lightweight & visual 5.Incremental releases 6.Frequent delivery of products 7.Complete each feature before moving on to the next 8.Apply the 80/20 rule 9.Integrated Testing 10.Collaborative & cooperative approach P.I.C.S

Requirements and Architecture E-R Diagram P.I.C.S

Requirements data dictionary P.I.C.S Database Schema

Story Board P.I.C.S

Story Board P.I.C.S

Tools and Technologies  MS SQL 2008  Visual Studio 2012  TortoiseSVN  Araxis Merge  Ultra Edit  Enterprise Architect P.I.C.S

Business Process Diagram P.I.C.S

Requirements and Architecture Use case Model P.I.C.S

Requirements and Architecture Sequence Diagram P.I.C.S

Requirements and Architecture Activity Diagram 1 P.I.C.S

Requirements and Architecture Data Flow Diagram P.I.C.S

Quality Control  Internal review Spell check and functionality. IEEE Standards-Documents.  Coding  Testing Unit testing- methods Test case scenario – done on each module P.I.C.S

Any Questions ? Thanks for attending the Presentation Team PICS P.I.C.S