Team L -final12

  • Uploaded by: srikanth546
  • 0
  • 0
  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Team L -final12 as PDF for free.

More details

  • Words: 413
  • Pages: 16
Under the Guidance Of Dave W Farthing, Chris Gold Faculty of Advanced Technology

       

Mr P M Roules (Project Manager) Mr J Cash (Financial Director) Mrs I Countem (Accountant) Mr T Rustmee (Salesman) Dr Anne Orack (Information Systems Manager) Ms Lynne O’Code (Senior Programmer) Ms Melody Cellar (Subscriptions Manager) Mrs Wilma Songster – Hart (Music Production Manager)

 Satish

babu gudapati

 Srikanth  Sagar

katragadda

kotaru

 Suneeth  Sarvani

tatineni

koneru

 Required  Project

Outputs

Objectives

 Activities,

Resources, Responsibilities and

milestone  Documentation  Periodic

Update of Reports

 Rockify's,

a well known and longestablished international business with more than 12 million customers and 1.4 million catalogue items.

 Rockify's

use HAL i-mini computers on which the present software runs.

 Requirement

of a secondary EPOS middleware from Gordon Handel Inc (GHI).

 Improve

Rockify's customer relationship management  Improve the EPOS system by installing a new software system  Install the new online music website.

 To

include necessary review of business processes  Deliver change rather than replicate current status.  Led by user requirements  Support and facilitate Rockify's e-commerce website  Integrate secure database  Capable to satisfy future requirements also.  User friendly interface

Common problems in projects  Lack

of communication and structure

 Difficulty

in involving the project members,

the customers, the procurer and other stakeholders.

monitor the quality control procedures  special responsibility for each stage of the project.  Regular project meetings for detailed study of user requirements. 

Assumptions No compromise and no warranty on the project plan.  Constraints 

o speed and structure of entire project team o Availability of users to work with project team o Time duration for completion of the project

Project Initiation Document  End user testing plan  Contracts with implementation partners.  scripts and report of outcomes  Project closure report 

Promoting corporate culture  Increase ‘brand image’ of University.  Provide a robust and supported system. 

 Satisfies current and future customer requirements incorporate future statutory changes

Failure to configure the system in time for the deadline  Potential for escalation of costs  Security (e.g. data protection over web). 



Ayres, R. (1999) “The Essence of Professional Issues in Computing”, Prentice Hall 



Lumbly, S. Jones, C. (2003) “Corporate Finance Theory and Practice”, 7th Ed., Thompson Learning 



Yourdon, E. (1989) “Structured Walkthroughs”, 4th Ed., Yourdon Press

QUESTIONS ???

Related Documents

Team L -final12
June 2020 1
Final12
June 2020 2
L L L L L.docx
April 2020 58
L L L L L.docx
December 2019 75
Team
May 2020 20

More Documents from "erizos"

Team L -final12
June 2020 1