Assesment 1

399, Lonsdale Street, Melbourne Vic 3000. Tel: 0945685123 Fax: 0954632147 E-Mail: [email protected] Web: www.pinnaclesol.com

Assignment 1 Pinnacle’s E-Library

Team members Asanka Ranaweera Chamila Roshani Perera Ho Dang Jasjit Kaur Kunalkumar Lamba Shivangi Kulkarni

: : : :

: 11402543 11401087 11408402 : 11400540 11408056 11408697

Pinnacle’s E-Library

Table of Contents Vision 1. Introduction................................................................................................................3 2. Positioning..................................................................................................................5 2.1 Problem Statement...............................................................................................5 2.2 Product Position Statement..................................................................................6 3. Stakeholder Descriptions............................................................................................6 3.1 Stakeholder Summary..........................................................................................6 3.2 User Environment................................................................................................7 4.4 Alternatives and Competition............................................................................11 4. Other Product Requirements....................................................................................11 1. Introduction........................................................................................................13 2. Project Organization...........................................................................................13 3. Development Process and Measurements ..............................................................15 4. Project Milestones and Objectives..........................................................................16 References:..................................................................................................................27

Page 2 of 27

Pinnacle’s E-Library

Pinnacle’s E-Library (Version 1)

1.Introduction Pinnacle’s E-Library will be a Web based application that manages the day to day transactions of Stafford College’s library. The college needs an electronic test application for its library that will benefit teachers, administrative staff and the students. They need a database to store, update, edit, delete and manage data. The Page 3 of 27

Pinnacle’s E-Library Administrative staff, teachers and students will be able to perform activities such as reserving books, searching books, generating various reports according to their authority level.

Page 4 of 27

Pinnacle’s E-Library 2.Positioning 2.1Problem Statement The problem of

• • • • • •

More time consuming in recording all transactions manually. Students have to wait in queues for long time to borrow books. Students can not reserve or search books out side the school premises. Difficult to track students who do not return books. Incorrect data recorded by library staff. Difficulty of creating various reports.

affects

•

Stakeholders are: Teachers, Students, Administrator, Project Manager, Developer and Analyst, Software distributors, client (CEO), Sponsors

the impact of which is

•

Students and teachers can access the system at anytime from any where.

•

Borrowing or reserving books can be done within few seconds.

•

Library staff can find out the students and fine them if they do not return books on time.

•

Less chance of data to be inaccurate.

•

Useful reports will be generated within few seconds.

•

An online system where students and teachers can reserve or borrow books even from the out side of the school. The new system is capable of tracking students who have pending fines. The system has the ability of generating various reports.

a successful solution would be

• •

Page 5 of 27

Pinnacle’s E-Library 2.2Product Position Statement

For

School purposes

Who

• Teachers • Students • Administrative staff Pinnacle’s E-Library

The (product name) That

Unlike

Our product

• • • • • •

Fast response time Database Driven Website. Accurate recording of Data. Frequently generated reports Update/Delete and adding functions. Less administrative work for staff (paperbased system) • Reports. (manually generated) • Time factor Electronic system which allows direct access from remote location (unlike being in classroom)

3.Stakeholder Descriptions 3.1Stakeholder Summary

Name Asanka Ranaweera

Description Project Manager

Chamila Roshani Perera

Analyst & Test Plans Developer

Page 6 of 27

Responsibilities • monitor and ensures project deliverables • ensures that there will be a market demand for the product’s features • monitors the project’s progress • approves funding • Analyses architectural requirements • design and demonstrate the architecture and to develop test plans • Prepares and/or maintains documentation pertaining to programming • user documentation and translates business specifications into user • documentation

Pinnacle’s E-Library

Ho Dang

Tester & Designer

•

• Jasjit Kaur

Analyst & Database Designer

• • • • • •

Kunalkumar Lamba

Developer and Designer

• • •

Shivangi Kulkarni

Developer and Designer

• •

•

test all the code and generate the bug reports using given test plans implement solutions design the architecture of the system Analyses architectural requirements design the architecture design the solution Responsible for designing and creating the database also take part in the programming Responsible to design the architecture of the system develop the code for the system take part in the development of the documentation & the database Responsible to develop the code and the test plans for the system Additionally she is also responsible for the documentation of the system take part in designing the architecture of the system

3.2User Environment

•

The number of people involved in the project is six which includes the Project Manager, Analyst, 3 developers and one person for testing the system. So far, each and everyone have their respective roles in the project and the number of people is not going to change.

•

Each task cycle is going to take approximately 20 days. Altogether the project will be delivered in 5 months. The duration might change Page 7 of 27

Pinnacle’s E-Library

•

•

Platforms in use are Windows 2000 / 2003 server, Windows XP on client machines.

Product Overview

4. 4.1

according to further implementation or with the fact of finishing the project earlier. There are some constraints in completing the project which are as follows: 1. Must be a Web based system 2. Cross browser compatibility 3. Use of MySQL Database 4. Use of PHP to connect to the database 5. The team must only use software that is properly licensed to develop the system 6. Time constraints imposed by Stafford College. The project has to be completed in the set time framed, i.e. approximately 5 months.

Product Prospective •

The application is specifically developed for library activities, transactions and there is no link between other systems.

Application works as follows •

Administrator will have the authority to create staff accounts with relevant rights, reverse transactions, maintaining backups and publishing and accommodating new changes to the existing system. In addition to that administrator is also responsible for Maintaining database and performing common tasks of the database such as monitoring log files of the database, size of the database, etc

•

Library staff will have to enter student details to the system, delete students, run reports daily , weekly and monthly as they needed, Sending reminders to students, etc

•

Authorised students can reserve a book online, check the status of the reserved books, due dates, request for new books, etc

4.2

Assumptions and dependencies •

Late changes/modifications to the system If the team feels new changes to be accommodated to the system, Project may not deliver the agreed schedule. Team will have to work on the revised project plan.

•

User friendliness of the system

Page 8 of 27

Pinnacle’s E-Library As we are highly concerning of the user friendliness of the system, if there are any suggestions from end users to improve the user friendliness we will modify the system accordingly. This will directly effect to project completion.

•

Incompatibility of browser and OS Software should work regardless of the current platform that they used now. Otherwise browse upgrade is needed for client computers.

•

Disturbance and Busy schedule for team members If there are more disturbance occur during the project development time, project may fall behind the schedule

4.3

Needs and Features

Page 9 of 27

Pinnacle’s E-Library Need

Priority

Features

Strong Security with three levels of access

Priority 1

Provide password s After 2 weeks prior renewals. to commencing the project

Database Implementation (My SQL) Accurate recording of data Robust system that does not crash

Priority 1

After 2 weeks

Robust system that does not crash

Priority 1

Decentralized Administration (Delegation of work)

Priority 2

Use of MySQL Database Parallel action Build a robust system with backup Build a robust system with backup Decentralized Administration and Administrative tasks

Cross browser compatibility (at least IE Explorer & Firefox) Fast response

Priority 3

Test & run on different platforms

After 2 weeks

Priority 2

Make response fast

After 4 weeks

Backup the database

Priority 1

Backup on another hard disk

From the 1st day project commence

Administrator is able to create / delete / update books

Priority 3

Add, delete, update After 5 weeks books

Administrator is able to create / update/ delete library members Library staff is able to handle issues and returns of books in the system Administrator is able to update fines in the system

Priority 3

Add, delete, update After 5 weeks library staff

Priority 3

Issues and returns of books

After 5 weeks

Priority 4

Update fines

After 6 weeks

Students are able to reserve books online

Priority 5

Online reservation

After 7 weeks

Report manager

Priority 6

Reports

After 8 weeks

Change password option

Priority 7

After 9 weeks

On line help

Priority 7

Users are able to change their passwords Help function

Priority 1 Priority 1

Page 10 of 27

Planned Release

After 2 weeks After 1 week After 1 week After 3 weeks

After 11 weeks

Pinnacle’s E-Library 4.4

Alternatives and Competition

Alternative product identified is: Library Gold - Kelowna Software Below are some of the features of the product: • Restart options if host connection is lost • Online reservation • Notifications for students about books to be returned • Notification for staff about outstanding fines and pending books • Automatic fine calculation • Allow students to hold / renew books from any where • Most wanted books

4.Other Product Requirements Design constraints:

• • • • • • •

Must be a Web based system Cross browser compatibility Use of MySQL Database Use of PHP to connect to the database The team must only use software that is properly licensed to develop the system Time constraints imposed by CSU. The project has to be completed in the set time framed, i.e. approximately 5 months. For new and existing users, an online help will be provided for easier use and management. A user manual as well will be designed as a backup to the online help and technical support.

Manuals: • Online help will be provided • User manual will be designed and distributed accordingly

Page 11 of 27

Pinnacle’s E-Library

Pinnacle E-library Solutions (Version 1)

Page 12 of 27

Pinnacle’s E-Library

1.

Introduction The project plan document devised below will describe the software project undertaken by the Pinnacle Solutions Ltd.

2.

Project Organization There are six project team members so far that will be guiding the e-library project to success. The team members are: Team member 1: Asanka Ranaweera – Project Manager Leads the planning of the project, coordinates interactions with the stakeholders, and keeps the project team focused on meeting the project objectives. Assesses results, plans iteration, manages iteration and plans project. He is responsible to all the purchases of material and equipments which are required for the project development. He is accountable for the overall success of the project within the given timeframe and resources. Responsible for the iteration plan, vision statement document, status Assessment and implementation. Team member 2: Chamila Roshani Perera – Analyst & Test Plans Developer Analyzes architectural requirements, design and demonstrate the architecture and to develop test plans. Prepares and/or maintains documentation pertaining to programming, user documentation and translates business specifications into user documentation. Plans, writes, and maintains systems and user support documentation efforts, including help. Responsible for the vision statement, supporting requirements, test cases and build Team member 3: Ho Dang – Tester & Designer Responsible to test all the code and generate the bug reports using given test plans. Additionally he will take part to design the architecture of the system. Responsible for the glossary, design, test logs, developer test.

Page 13 of 27

Pinnacle’s E-Library

Team member 4: Jasjit Kaur – Analyst & Database Designer Analyzes architectural requirements, design the architecture, design the solution. Responsible for designing and creating the database and also take part in the programming. Responsible for creating for the project plan, actors, use cases, use case model and build. Team member 5: Kunalkumar Lamba – Developer & Designer Responsible to design the architecture of the system and to develop the code for the system. Additionally he will take part in the development of the documentation & the database. Responsible for the risk lists, architectural proof-of-concept and test scripts. Team member 6: Shivangi Kulkarni – Developer & Test Plan Developer Responsible to develop the code and the test plans for the system. Additionally she is also responsible for the documentation of the system and she will also take part in designing the architecture of the system. Responsible for the work items lists, architecture and test cases. Team member

Project Manag er

Asanka Ranaweer a

X

Chamila Roshani Perera

Analy st

Databas e Designe r

Code Develop er

X

Test Plan Develop er

X X

Teste r

X

Ho Dang Jasjit Kaur

Design er

X

X

Kunalkum ar Lamba

X

Shivangi Kulkarni

X

Page 14 of 27

X X

Pinnacle’s E-Library

3.

Development Process and Measurements The reference process to be used is OpenUP/Basic which stands for (Open Unified Process). OpenUP divides the project into iterations: planned, timeboxed intervals typically measured in weeks. Iterations focus the team on delivering incremental value to stakeholders in a predictable manner. The iteration plan defines what should be delivered within the iteration, and the result is a demo-able or shippable build. OpenUP teams self-organize around how to accomplish iteration objectives and commit to delivering the results. They do that by defining and "pulling" fine-grained tasks from a work items list. OpenUP applies an iteration lifecycle that structures how microincrements are applied to deliver stable, cohesive builds of the system that incrementally progresses towards the iteration objectives.

OpenUP is characterized by four mutually supporting core principles:

•

Collaboration and communication

•

Management

•

Intent

•

Solution

Features and benefits

•

Iterative and risk-driven

•

Minimally sufficient for small allocated teams

•

Flexible to meet the needs of larger teams and more intricate environments

•

It supports guidance (checklists, templates, guidelines, examples)

Methodologies in OpenUP/Basic in use

OpenUP structures the project lifecycle into four phases: Inception, Elaboration, Construction, and Transition. The project lifecycle provides stakeholders and team members with visibility and decision points throughout the project. This enables effective oversight, and allows you to make "go or no-go" decisions at appropriate times. A project plan defines the lifecycle, and the end result is a released application. The following are the four phases of the project lifecycle:First phase in the project lifecycle, it is about understanding the project scope and objectives and getting enough information to confirm that the project is feasible. Inception:

Page 15 of 27

Pinnacle’s E-Library Second phase in the project lifecycle, where the baseline of the architecture of the system is established and it provides a stable basis for the whole of the development effort in the next phase. Elaboration:

Third phase in the project lifecycle. This focuses on design, implementation, and testing of functionalities to develop a complete system. Its purpose is to complete the development of the system based upon the base lined architecture. Construction:

Transition: The fourth and final phase in the project lifecycle. The purpose in this phase is to ensure that the software is ready for delivery to users. In terms of tracking the progress of the project a number of techniques will be in use: • • • • 4.

Regular team meetings to measure the progress Time to time update of project documents Use of a work breakdown structure to help prioritize the needs of the project Liaison with the client to manage the scope of project

Project Milestones and Objectives Phase

Iteration

Primary Objectives (risks/use case scenarios)

Scheduled Start/Milest one

Target Velocity

Inception

I1

Objectives

25/07/08 to 22/08/08

45

23/08/08/ to 10/10/08

55

Inception (Lifecycle Objectives Milestone)

I2

•

Project Plan

•

Work Item list

•

Risk List

•

Vision document

•

Glossary

Objectives

•

Iteration plan

•

Risk list

•

Work Item list

•

Supporting requirements

•

Actor

•

Use cases

Page 16 of 27

Pinnacle’s E-Library

Inception (Lifecycle Objectives Milestone)

I3

•

Use case Model

•

Test cases

•

Architecture

•

Design

•

Architectural Proof of concept

•

Status assessment

Objectives

•

Iteration plan

•

Risk list

•

Work Item list

•

Supporting requirements

•

Actor

•

Use cases

•

Use case Model

•

Test cases

•

Architecture

•

Design

•

Implementation

•

Build

•

Developer Tests

•

Test Scripts

•

Test Logs

•

Status assessment

Page 17 of 27

11/10/08 to 07/11/08

65

Pinnacle’s E-Library

Pinnacle E-library Solutions Risk List (Version 1)

Page 18 of 27

Pinnacle’s E-Library

Page 19 of 27

Pinnacle’s E-Library

Pinnacle E-library Solutions Work Items List (Version 1)

Page 20 of 27

Pinnacle’s E-Library

Page 21 of 27

Pinnacle’s E-Library

Pinnacle E-library Solutions Glossary

Page 22 of 27

Pinnacle’s E-Library

A Administration Function: that is tasks which admin can do when the system operate Administrator: people who have the responsibility to manage the system of library Architecture Proof-of-Concept: that is a outline or idea about functions which will be had in the software or system. B Bug Report: that is report which will be showed mistakes which programmers who will fix these with purpose make the software correctly. C Construction: this is concentrate about design, implementation and test in the project lifecycle with the purpose to complete the system. Critical Feature: that is the feature which is important or necessary D Database: that is data about information which use for the library and user can use it and it is stored in computer Decentralized Administration: this is divide tasks which administrators, users or staffs can do on the system. Disaster Recovery Procedure: that is a document which is showed what work will do after the disaster that is used to recovery the system. E Elaboration: this is used to provide a stable basic which will be helped for team project know what is must do before the next task will do. Evaluate risks: that is the changing of risk to third party who will have responsibility to resolve the risks for example the insurance company. F G H I Inception: this is used for the purpose which will be helped team member know about scope and information about object in the project. Iteration Lifecycle: that is a method which is used for purpose rework all tasks in lifecycle of processing the project. Iterative Development: this is method which is used to rework the task that is made before. This is important because it is helped the task increase the quality the task and support some feature that did not get in the previous or it is made the task more efficiently. Iteration Plan: this is provided the team member about information of iteration objectives, detail plan with tasks must be done and rating result. J Join Application Development (JAD): that is technique which is used to take the user into the development processing the project as a member does the project K L Liaison: this means all tasks which make the complete the project. Library Staff Function: that is tasks which staff can do when they work in the library

Page 23 of 27

Pinnacle’s E-Library M Mission Critical System: that is a system which does not have the failure in the operating Mitigation Strategy: some way which can be use to decrease the risk Monitoring Log File: this is used for looking for specific log file which the purpose to check error information that you want to know MySQL: this is a program which runs as a server with the purpose is supporting for many users who can access to database. N O OpenUp (Open Unified Process): this is an Open source which is used to provide a set of perspective and development needs. OS (Operating System): that is software which is used for processing the system for example: Window and Linux. P PHP: this is a scripting language which is used for design dynamic web pages (server-side scripting) Project Charter: this is a documentation which will show information about scope, object and participants in the project for instance role and responsibility of team member in the processing the project. Project Funding: that is cost which use to processing the project Project Manager: people who to manage the project and the people have responsibly about project. Project Plan: that is an outline an agreement of members about the project which will be processed. Project Sponsor: people who to take the final decision about the project and view important reports which are made by project manager. Prototype: this is a type, form or something which is value basic or outline for example the image the website which is demonstrate the web page that look like as the image when the design the web site complete Proven Tool: Proven tool is a verified tool that is used to re-estimate the project. Q R Renegotiate Scope: that is the change a little about the scope that is usually occurring within the processing the project. Risk List: this is a list risks which is known and an open list of risks can add to the project which can affect the successful of the system. Robust System: this is a system which can alarm mistake or report information about threat can make the system down. S Server: the main computer which use to manage the system or network Senior Management: that is person who has the highest level of the organization or company, this person has the responsibility to manage the operating the company or organization. Sponsor: that is person who will provide the support. Stakeholder: that is person who holds the important information which can use in the project Status Assessment: this is a document which is used for review, summary and analyzing about information of the processing of software.

Page 24 of 27

Pinnacle’s E-Library T Team leader: people who manage a group which work on the project Team member: people who work on the detail tasks of the project Test Case: this is a set of conditions or variable which the tester will define. Test Logs: this is used to share information among testers, clients, developer and someone who do the project. It is conclude detail about acting of each test case. Test Script: this is a set of instructions which is used to check the system functions. Tester: person who will test the system or software Timeframe: this is the specific time which is used for the purpose make the software has more valuable. Transition: this is a final part in the project lifecycle which is used to ensure that the software is ready to support to users, client or customers. U Update Fine: this is generation update information. Use Case: this is a description about the system which has processes or responds from requests of users. Use Case Model: this is a model that is showed information about system’s function requires following by use case. User: the person use the service of library User Function: that is tasks which student can do when they use service of the library V Vision: that is required or demand of users and customers which product will be used to develop the system and the specific is conditions of key stakeholder needing and features of the program. W Work Breakdown Structure: this is documentation which show detail about tasks and time complete these tasks. This is very helpful because it is showed for everyone to know about what task is done or task need more time to complete. Work Item List: this is a list of tasks which must to be done when the project is processed. X Y Z

Page 25 of 27

Pinnacle’s E-Library

References

Page 26 of 27

Pinnacle’s E-Library References: Cadomel Library System n.d, “Library Gold”, viewed on 2nd August 2008 Capterra n.d, “Library Automation Software Directory”, viewed on 7th August 2008, Capterra n.d, “Library Automation Software Directory”, viewed on 7th August 2008, Eclipse n.d., “Eclipse Process Framework Project (EPF)”, viewed on 28 July 2008,

Page 27 of 27