Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

OLYMPIC ELECTRONICS
ELECTRONIC SHOP PORTAL

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Table of Contents
Introduction ................................................................................................................................3 Project Scope ..............................................................................................................................3 Summary of the solution .........................................................................................................3 Project objectives ....................................................................................................................4 Roles and responsibilities ........................................................................................................4 Change control process ...........................................................................................................5 Project Planning ..........................................................................................................................6 Overview of the Work Breakdown Structure ...........................................................................6 Work Package 0 Project Management..................................................................................6 Work Package 1 Analysis (WP1) ...........................................................................................6 Work Package 2 Design (WP2) .............................................................................................8 Work Package 3 Implementation (WP3) ...............................................................................8 Work Package 4 Verification and Testing (WP4) .................................................................10 Deliverable Definition Table ......................................................................................................10 Deliverables Structure Chart ..................................................................................................13 Reference List ........................................................................................................................13

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Introduction In our previews part of the portal and assignment creation, we analyzed some serious issues using a remarkable tool of project and software development which was the feasibility study. In this step the project will be examined through the scope of project scope and planning. In the Project Scope part, a solution will be provided about what of the activities mentioned in the feasibility study will take place. It will be mentioned which of them are high or low priority activities, as also the project objectives as are the hardware, the network and the software parts and the roles and the responsibilities of each key stakeholder of the project. In this section it will be described which are the team leader, project manager, developers, and network engineers. In the Project Planning part, an overview of the work breakdown structure will occur, the deliverables and the activities created in the Gantt Chart with the aid of Microsoft Project will be described, and finally a list of references.

Project Scope
Summary of the solution

The organization name of the project is Prototype Electronic Shop. This project is about the building of a WEB SITE for the OLYMPIC ELECTRONICS Co. The scope management helps to determine what is and what is not included in the project work. This sets the work boundary for the project and identifies the project deliverables and the product deliverables (the features and functionality of the solution). Once the scope is well defined, the project team focuses on what really

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

needs to get done and what is outside the scope of the project, and as a result this leads to efficient waste of time and resources

Project objectives

This web site is to serve as a brochure for the products of the OLYMPIC ELECTRONICS, in many cost-effective ways. This strategic solution aims at the increase of the products sales, and at the increase of the marketing efforts, especially on the Internet. These project objectives align totally with the MOV (Measurable Organizational Value) that has been defined in the feasibility study of this project. As we well define the scope management plan, the work to be performed is going to add any values to the Corporation. So the time and the resources are going to be consumed effectively, according to the scope.

Roles and responsibilities

The key stakeholders of the project are the team leader, the Project Manager, the development team, the implementation team and the security team. The team leader has to create a friendly environment with good communication skills. He has to motivate and inspire his co-workers. Also he has to be the role model of the company, so that the others can do the same. He is responsible for orientating the groups so that they can work harmoniously and effectively together solving problems of any group. Creativity, risk taking and coaching are some of the characteristics that the team leader should have. The project manager is the person who has the responsibility to lead the plan to success, and the fruitful execution of it. He should have many skills, such as the ability to foresee with experience, methodology, and stability any problems that would occur during the execution of the plan, and to be fast enough and smart to detect them and solve them finally with success.

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

The development, implementation and security team are in charge of assembling correctly and methodically the whole project and setting up the WEB SITE in accordance to the requirements of the OLYMPIC ELECTRONICS Co. They also, will always have to keep in touch with the WEB SITES server, so that they can maintain, upgrade, or fix any possible problems that might occur in any time due to different parameters.

Change control process

Scope Management will be the sole responsibility of the Project Manager. No changes will be allowed unless authorized by the Change Control Board. The Change Control Board will be comprised of the Project Sponsor, and the key user (stakeholders). The administration of the changes will follow the procedures of the Corporate Change Control System. Since the main function of this WEB SITE is to serve as a brochure, it is not expected that many changes will be requested. We have specifically excluded the financial transaction capability. The Requirements Definition Document and the Design Document will finalize the details of the requirements. Any stakeholders involved in the Project can identify changes. Changes will be classified and prioritized as per criteria defined in the Corporate Change Control System:

Impact (Major, Medium, Minimal) Severity (High, Medium, Low) SEVERITY High Medium Low Major 5 4 3 Impact Medium 4 3 2

Minimal 3 2 1

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

All change requests must be submitted to the Corporate Change Control System, using the standard Change Request Form.

Project Planning
Overview of the Work Breakdown Structure Work Package 0 Project Management Work Package 1 Analysis (WP1)

The heading of this work package is ANALYSIS. The WP1 will consist of our first three parts of our coursework and project that is the Feasibility Study, the Project Planning and the Requirements phase. The feasibility study consists of three deliverables Business Requirements 2. Building the Feasibility Study Report and 3. Testing, Confirmation, Approve Plan First of all, the Business Requirements is an important deliverable that shows the contiguous parts of the project. It is separated in two subtasks that are the Administration and Customer Activities. The Administration Activities as mentioned in the previews part of the project is the localization of the teams that will be set to manage the project and the portal. One team has to be set to implement the project and one to control and manage the portal when done. In a first scope this wants one day to be decided for the both teams. The Customer Activities are all about the requirements of the clients. It will be set how the customers will behave inside the portal and what their role will be on it.
1.

The Building Feasibility Study Report is all about the preparation of a full report that will show the necessary needs and risks. It is divided in two subtasks that are the most important of it, the Business Processes Support and the Measurable Organizational Value (MOV). The Business Processes Support identifies how the system is indented to support these processes. The Measurable Organizational
6

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Value that shows strategies and market values. Four days per each of these subcategories total eight days are enough to complete the feasibility study report in one sight. The Testing, Confirmation, Approve Plan is the part of the budget management. This deliverable shows if the report will be approved by the electronic shop, if the project is within the budget and every risk faced is avoided or better controlled. The subtask of it is the Risk Management. It requires three days to examine all the potential risks found. The Project Planning deliverable includes the Project Objectives, Roles and Responsibilities 2. Project Process, Project Planning 3. Gantt Chart Errors Management The first part of Project Planning describes the objectives of project in a project scope, finds a solution and sets roles and responsibilities. This is the Project objectives, Roles and Responsibilities. This is a five days work that begins first in the timeline.
1.

The Project Process, Project Planning describes the whole process of creating the project. It has work packages in it, deliverables, Gantt chart and diagrams. This is estimated for a six days job and starts after the first part simultaneously because they fulfill each other as subtasks. The Gantt Chart Errors Management deliverable is the creation of the Gantt chart itself, and reviewing work for unnecessary errors in management of days. The Requirements deliverable includes: Requirements Elicitation 2. Requirements Specification 3. Requirements Validation and the last one 4. Functional and Non Functional Requirements Requirements Elicitation is the method by which the requirements for the project are discovered and overall system models can be produced. It describes which are the stakeholders and end users, open close interviews and some scenarios use cases.
1.

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Requirements Specification is the means of converting the requirements into a standard form resulting in the user and system requirements. It includes the user and system requirements. Requirements Validation is the means of defining whether the requirements actually define the system that the customer wants, resulting in a requirements document. In simple words, it includes the validity checks, the consistency checks, the completeness checks, the realism checks, and the verifiability. Functional and Non Requirements

Work Package 2 Design (WP2)

The Design work package is the part that talks about the graphical interface of the project. It has two main subtasks the Visual and Technical Design Strategy, and the Software Design. The Visual and Technical Design Strategy is all about the user graphic interface, in other words, of how the program will look? I t is includes the Prototype Creation Deliverable and the Visual Design. The Prototype Creation is the days that the first prototype of the portal will be created and presented. The visual design is the deliverable with the effects, the new technology that will be included in the graphics, and the innovation on the user environment. The Software Design contains the Graphical and Client Interface, and the Malfunction deliverables. The first one refers to the software that should be bought and used in order to achieve the primary objectives for the implementation of a new technology in graphics and design. The second one speaks about the technical issues of design problems, bad programming and etc.
Work Package 3 Implementation (WP3)

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

The implementation part in my opinion is the most important part of the project plan. Here everything is on the line and the management team can see if their calculations were correct or wrong. It has five main subtasks:

1. 2. 3. 4. 5.

Working Environment Teams for implementation Hardware Design and Implementation Network Design and Implementation Connectivity

The Working Environment is the subtask that concludes everything has to do with the room of the project. The Location of Properties is the deliverable that finds where the business, the warehouses, the rooms for the staff and team, the parking area for the new shipment is placed. The Saving Storage and Backup is the backup products location and where the database of shipment will be placed. Car Lot and Transport Area is the implementation of the parking zone for the trucks. The Rooms for Teams and Staff are the rooms of the teams for implementation. Teams for implementation are subcategorized in two more. The Management Teams Organization is the team for the implementation and the project creation. The Administration Team Supervisors is the team of administrators of the portal, the security parts, the shopping department, and the supervisors of them that will have full authority. Hardware Design and Implementation is the purchase of the hardware material. The Market Analysis HW is the search for the best profitable and loyal hardware that the team can buy within the budget. The Hardware issues part is about the defects or malfunction a hardware may show or wrong use. The Storage Info mostly is about the memory and the storage data that can be saved in the memory slot so the database and the products, the user interface can all be saved in it and have plenty of free room. Network Design and Implementation is the purchase of the network material. The Market Analysis NW is the search for the best profitable and loyal network stuff that the team can buy within the budget. Security and Protection Issues as
9

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

also the Anti Crime and Data Protection and Backup is the security of the portal. These deliverable have to be carefully designed in order that no competitive eshop or company enters or hits our own e-shop in order to steal or have as the result the loss of date, that could be very damaging for the portal. Backup Systems and Anti Hacking teams should avoid such results. Connectivity is the part that everything in the network and the hardware material is connected. Cabling is for the cables, multiplexing, optical fiber and Servers, Routers, Hubs, Switches and Access for the network.
Work Package 4 Verification and Testing (WP4)

This whole work package is to verify for the last moment before giving the final product in the air if everything is in order to start the production. Teams and Organization Verification verifies if the teams are the same as set in the analysis and the implementation phase. Teams for Design Verification and Implementation are the two subcategories, that for their names we can understand what they seek. Hardware/Software/Network Verification and Testing is the part that all of the hardware, software, network material will be verifies for their working and test if they give the expected results. Graphical User Interface, Access Testing is the part that the user interface is checked for bug errors, access malfunctioning and database unrecognizable errors and etc. Budget Verification is the part that the risk is mentioned for the last time if any and we try to avoid any of it. Loss of money will drive the project management team to a bad reputation. Profit will be in our advance and return for any extra money. Final Testing of the portal when everything is in order and working. Deliverable Definition Table I will not include all the deliverables as analytically as I did in the below section of the first page to all the Deliverable Structure chart because I do not wish of
10

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

repeating unnecessary things, but I will include the deliverables that structure is different than document. The other deliverables that will not be included can be found in the Gantt chart.

Deliverable ID D 1.1 D 1.1.1 D 1.1.2 D 1.2 D 1.2.1 D 1.2.2 D 1.3 D 1.3.1 D 1.4

Title Business Requirements Administration Activities Customer Activities Building Feasibility Study Report Business Processes Support Measurable Organizational Value Testing, Confirmation, Approve Plan Risk Management Project Planning

Structure Document Document Document Report Document Chart Document Contract Document

Resources Developer Team #1 Developer Team #1 Developer Team #1 Developer Team #2 Developer Team #2 Developer Team #2 Developer Team #3 Developer Team #1 All Developer Teams All Developer Teams Developer Team #2 - Developer Team #3 All Developer

D 1.4.1

D 1.4.2 D 1.4.3 D 1.5

Document Report Charts Project Objectives, Document, Roles and Discussion Responsibilities Project Process, Project Document, Planning Schema Gantt Chart Errors Chart Diagrams Requirements Discussion, Interviews,

WP Due Date 1 1811-11 1 1611-11 1 1811-11 1 3011-11 1 2411-11 1 3011-11 1 1711-11 1 1711-11 1 1612-11 1 0512-11 0712-11 1612-11 1001-12
11

1 1 1

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Teams D 1.5.1.2 1 211211 D 2.1 Visual and Technical Software, All Teams 2 24Design Strategy material, data, 01Graphic Design 12 D 2.1.1 Prototype Creation Software, data Developer Team #1 2 240112 D 3.1 Working Material, Base, All Teams 3 24Environment Document 0212 D 3.1.1 Location of Material, Developer Team #1 3 16Properties Document 0212 D 3.1.4 Rooms for Teams Material, Developer Teams, 3 22and Staff Document, Administration Teams 02Graphic Design 12 D 3.3 Hardware Design and Hardware Implementation 3 27Implementation Material, Teams 03Document, 12 Data D Anti Crime Issues HW/SW/NW Security Team 3 163.4.2.1 Material 0312 Open/Close Interviews Interviews, opinions All Teams

D 4.1

D 4.2

Teams and Organization Verification HW/SW/NW Verification

Contracts, Report Report, Material,

All Teams, 4 Administration and Security Develop, 4 Implementation

160412 300312

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

D 4.3

Graphical interface Testing Budget Verification

Data Test Plan User Report, Material, Test Plan

D 4.4

Teams, Testers (like clients) Develop, 4 Implementation Teams, Testers (like clients) Report, Excel Develop, 4 Sheets, Implementation Document Teams MILESTONE OF 10 DAYS Every Unit

12 160412 130412

FINAL FINAL TESTING

Milestone 100412

Every Milestone in the Gantt chart has the structure of a contract and is for verification purposes.

Deliverables Structure Chart

The chart is included in the .rar file in built in MS Visio.

Reference List

http://www.profsr.com/msproject/msproj01.htm http://www.youtube.com/watch?v=f2tQLHD1cRk http://www.project-tutorial.com/ http://management.about.com/od/PMterms/g/Project-Scope.htm http://en.wikipedia.org/wiki/Scope_(project_management)

13

Prototype Electronic Shop January 10, 2012

Stefanis Pavlos, Anastashs Konnarhs, Xhani Trungu

Tutorial from Class http://www.techrepublic.com/blog/project-management/define-project-scope-to-includedeliverables-boundaries-and-requirements/151

14