*

Fahad Zafar Mudasar Ellahi

*The social networking website is an online

community designed to make social life more active.

*This website also provides the features of

blogging. The main idea behind blogging is to share your thoughts with all your friends which can be read by all the users using the website.

*This blog can be handled by the user as he wants

.It also provides the features of adding videos and photos.

* Scrum is an agile, lightweight process that can

be used to manage and control software and product development using iterative, incremental practices

*Status meeting with all stakeholders. *Increments are delivered. *Problems are reported. *ANYTHING can be changed, work can be
added, eliminated, re-prioritized.

*New estimates and team assignments

are made for the next Sprint.

* The Product Owner: * Our product owner is the Arid Institute * The Scrum Master:
* Scrum Master Mr.Yasir Hafeez
* Consult with the Product Owner and the Team

* The Team
Roles

*
Assigned to

* Owns the production and engineering process

Project Manager Design Engineer Implementation Manager Training Lead Functional Manager Department Manager

Fahad Zafar Mudasar Ellahi Hassan-ul-Islam Mubashir Nazir Ali Hasnain Arslan Naeem

Develop Social Networking Website, The AridBook in which aridians will be able to blog, share, message.

* List of features of our Social Networking System

under consideration * Business features and technology features * FE-1: Create/Delete Profile * FE-2: Update account * FE-3: Get forgotten password through Email * FE-4: Message system * FE-5: Blog system * FE-6: User login/Logout

* Sprint
* Will Last for about 30 days * Implement the top priorities in the Project
Backlog called as the Sprint Backlog

* Sprint 1: Create/Login/Logout * Sprint 2: Account Maintenance * Sprint 3: Message System * Sprint 4: Blog System

* Last about 15 minutes * Following are the questions asked by the scrum
master

* What was achieved since the last meeting? * What are the impediments to your tasks? * What will you achieve before the next meeting?

* The Product Backlog * The Sprint Backlog * The Product Increment

* Lasts for about 4 hours * Feedback to the management * Feedback to the next Sprint

* Time boxed to three hours. * Team, Scrum Master, and (optionally) Product
Owner review the last Sprint

* Actionable items are presented to the Product

Owner for prioritization as non-functional requirements.

* A Functional Requirement defines a function

of a software system or its component.

* Following will show the complete list of

functional requirements of our site.

* FR-1: * FR-2: * FR-3: * FR-4: * FR-5: * FR-6: * FR-7: * FR-8:

Create/Delete Profile Update account Get forgotten password through Email

Message system (Write/Delete on own/others wall) Search members /add as member/delete member Blog system (add/modify/delete posts) Add comment on others blog post Post and search classifieds.

*FR-9: User login/Logout *FR-10: Add/ Delete/Modify Photo Galleries *FR-11: Add/ Delete/Modify Video Galleries *FR-12: Update/add/delete company

information, Site administration to manage site content like Admin Users Members, Pictures, Videos, Music, Blog, Categories, Blog ,Posts.

* Purpose:
oThe Plan is a contract between the Project Manager,
Executive Sponsor, Project Team and other management of the enterprise associated with and/or affected by the project.

oEach Project Plan component is essentially a work

product resulting from subtasks in the Make Plan Project Management task, but can be revised during other project management activities.

* Design and Implementation Constraints

oSecurity: The system should take care of hacks.
It should also not expose any sensitive information to normal users.

oFault Tolerance: Data should not become

corrupted in case of system crash or power failure.

* Assumptions
oCentral server of the system must be able to
handle all the incoming requests simultaneously.

oBack up of the databases in case of hardware

failure, disaster, natural calamities.

oNo data loss in case of handling of the system by

the administrators or the system related personnel

*
*Project Schedule
S.No
1 2 3 4 5 6

Process/Phase
Requirement Gathering Requirement Analysis Screen Design Pseudo code Coding Testing

Start Date
01/01/2012 01/02/2012 01/03/2012 01/04/2012 01/05/2012 01/06/2012

End Date
01/02/2012 01/03/2012 01/04/2012 01/05/2012 01/06/2012 28/06/2012

* Milestones
Time Frame 15 days 30 days

Milestones Business Requirements and Project Scope documentation Product Perspective, Requirement Analysis and Product Functions Design and Use case

10 days

* Project Budget
Cost Type Cost (Rs) 1,00,000 50,000 20,000 30,000 2,00,000

Fixed Costs Material Costs Contractor Costs Management Reserve Total Project Cost

* Quality Management

*For an information system, controlling

the consistency of screen layouts would include reviewing all screens to make sure they match the standards. *Quality measures ensuring that there are no bugs or defects for certain critical requirements, consistent screen layouts, or correctly calculating variables.

* Human Resource Management

The roles and responsibilities for the Software Upgrade Project are essential to project success. All team members must clearly understand their roles and responsibilities in order to successfully perform their portion of the project.

*
Roles Assigned to

Project Manager Design Engineer Implementation Manager Training Lead Functional Manager Department Manager

Fahad Zafar Mudasar Ellahi Hassan-ul-Islam Mubashir Nazir Ali Hasnain Arslan Naeem

Risk Management:

The project manager working with the project team and project sponsors will ensure that risks are actively identified, analyzed, and managed throughout the life of the project
*
RISK ANALYSIS

All risks identified will be assessed to identify the range of possible project outcomes.

RISK RESPONSE PLANNING

* * * * *

For each major risk, one of the following approaches will be selected to address it: Avoid eliminate the threat by eliminating the cause Mitigate Identify ways to reduce the probability or the impact of the risk Accept Nothing will be done Transfer Make another party responsible for the risk (buy insurance, outsourcing, etc.)

Communications Matrix
The following table identifies the communications requirements for this project Communicati Medium Freq Audience Owner Deliverable on

Project Team Meetings Technical Design Meetings Project Status Reports

Face to Face Conference Call Face-to-Face

Weekly

Project

Team

Team Lead Project Manager Project Manager

Meeting Minutes

As Needed

Project Technical Staff

Meeting Minutes Project Status Report

Email

Monthly

Project Sponsor Project Team Stakeholders PMO

Procurement Management

* *

Ensured that project team members are assigned computers Development and test servers are designed

Test Case Test Case ID: T-001 Wrote By: Fahad Zafar Test Type: Manual Product Name: Aridbook

Test Item: Enter url Doc Date: 1st January 12 Test Suite#: 001 Release and Version No: V1.0

Test case description: enter url in browser http://localhost/AridBook Pre-conditions: Server should be up and website should be accessible Post-conditions: Display the home Page with Registration, login Required test scripts (for auto): NA Cross References: R-001, UC-01

Test Case Test Case ID: T-002 Wrote By: Mudassar Ellahi Test Type: Manual Product Name: Aridbook Test case description:

Test Item: Edit profile Doc Date: 2nd Feb 12 Test Suite#: NA Release and Version No: V1.0 1)Click on "Edit Profile" Link 2)Modify the required data 3)Click on "Save" Button

Pre-conditions: Successfully login to system Post-conditions: Data Must be Updated Successfully Cross References: R-001, UC-01

Test Case Test Case ID: T-003 Wrote By: Ali Hasnain April 20 Test Type: Manual Product Name: Aridbook

Test Item: Log out Doc Date: 26th

Test Suite#: NA Release and Version No: V1.0

Test case description: 1) Click on "Logout" link Pre-conditions: Successfully login to system Post-conditions: System should send user to login page Required test scripts (for auto): NA Cross References: R-001, UC-01

Problem ID: B-101 Test type: Manual

Current software name: Aridbook Reported by: Fahad Zafar Test case ID: T-001

Reported date: 1st Jan 12 Subsystem (or module name): Login

Feature Name (or Subject): System Login Tab Problem type (REQ, Design, Coding,): Coding Problem severity (Fatal, Major, Minor,): Major Problem summary and detailed description: Home Page not displayed Cause analysis: NA How to reproduce? Why Required: Remove Code Error Attachments: Nil

Problem ID: B-101 Test type: Manual

Current software name: Aridbook Reported by: Fahad Zafar Test case ID: T-001

Reported date: 2nd Feb 12 Subsystem (or module name): Profile Feature Name (or Subject): Profile Tab

Problem type (REQ, Design, Coding,): Design Problem severity (Fatal, Major, Minor,): Major Problem summary and detailed description: Data not updated due to error in Database Connectivity Cause analysis: NA

How to reproduce? Why Required: Debug Database connectivity design Attachments: Nil