Online Photo Management System

1
Online Photo Management System

• MSE Project Presentation I-Sameera
  AvilalaMajor Professor Dr. Bill Hankley

2
Agenda

• P roject Overview
• Use case
• Project Requirements
• Cost Estimate
• Gantt Chart
• Architecture Elaboration Plan
• Work Breakdown
• Questions?

3
Project Overview

• Online photo management has become a very useful
  tool for uploading and sharing photos online in a
  very efficient way.
• Moreover, doing the design phase during CIS 764
  class gave the foundation for implementing this
  project.
• The motivation of the project also comes from my
  desire to learn the increasingly growing field of
  .NET, SQL server database designing and website
  designing.

4
Use Case Diagram
5
Example Yahoo Photos
6
Project Requirements

• Login
• Purpose The purpose of this part of the
  application is to enable user authentication. A
  valid user account must be used if you are an
  existing customer and a new customer can
  register.
• Input The user will enter two inputs (user name
  and password) through the keyboard.
• Processing The user inputs will be validated and
  authenticated by checking the user name and
  password to see if they match the data stored in
  the database.
• Output If the user name or password is invalid,
  the appropriate error message will be displayed
  and the user will be requested to re-enter user
  name and password. If the user inputs are valid,
  the main page will be displayed.

7
Sample screenshot
8

• Manage Profile
• Purpose The purpose of this part of the
  application is to enable user to manage his
  profile.
• Input The user will select his profile section
  and choose to manage his profile information with
  various options given.
• Processing The user selection will be validated
  and accordingly the action is being performed
  against the users account at the server. Profile
  is then updated accordingly at the server.
• Output The required action is being performed
  based on the selection of the profile name and
  other details.

9
(No Transcript)
10

• Manage Albums
• Purpose The purpose of this part of the
  application is to enable user to manage his
  uploaded albums.
• Input The user will select his albums and choose
  to manage the same with various options such as
  edit/delete/share/privacy settings etc.
• Processing The user selection will be validated
  and accordingly the action is being performed
  against the users account at the server
• Output The required action is being performed
  based on the selection of the action, between
  edit/delete/share/privacy settings.

11
Sample Screenshot
12

• Manage Photos
• Purpose The purpose of this part of the
  application is to enable user to manage his
  individual photos.
• Input The user will select his photos and choose
  to manage photos with various options given.
• Processing The user selection will be validated
  and accordingly the action is being performed
  against the photos selected at the server. Edit
  description, privacy settings and add details are
  the various options are being processed.
• Output The required action is being performed
  based on the selection of the option of the photo
  like edit description, privacy settings or add
  details.

13
Sample Screenshot
14
Cost Estimate

• The COCOMO model developed by Barry Boehm will be
  used to estimate project effort and project time.
  The Online Photo Management System will be an
  application of average complexity but with an
  extensive database.
• Effort 3.2 EAF (size)1.05
• Time (in months) 2.5(Effort)0.38
• Where
• Effort number of staff months (PM)
• EAF effort adjustment factor
• Size number of lines of code for completed
  product. It is measured in KLOC (thousands of
  lines of codes)
• Time total number of months

15
Cost Estimate(2)

• The EAF value based on the adjustment factors
  being assumed evaluated to 1.006. I estimated the
  size to be 1600 LOC based on the current
  prototype and similar examples. The effort
  evaluates to
• Effort 3.21.0061.61.05 5.27 staff months
• The time can now be calculated as
• Time 2.55.270.38 approx. 4.9 months

16
Gantt Chart
17
Architecture Elaboration Plan

• Revise Vision Document
• The vision document will be revised based on the
  feedback received on presentation I. The advisory
  committee will review and make required
  suggestions for the project. These suggestions
  will reflect in version 2.0 of the vision
  document. Presentation II will be the review
  stage of vision document version 2.0 and will
  require approval of the chief professors and
  other members of the advisory committee.
• Revise SQA Plan
• Similarly the SQA plan will also be revised
  accordingly to accommodate any required changes
  based on review and feedback from presentation I.
• Revise Project Plan
• Similarly the Project plan will also be revised
  accordingly to accommodate any required changes
  based on review and feedback from presentation I.
• Develop Formal Requirement Specification
• A detailed formal specification will be provided
  using OCL (object constraint language).

18
Architecture Elaboration Plan(2)

• Revise Architecture Design
• The architecture will satisfy the requirements
  specified and will be documented with the aid of
  appropriate use case diagrams, sequence, class,
  state, and collaboration diagrams.
• Develop Test Plan
• A detailed test plan will be defined listing all
  the tests that have to be performed so that the
  project satisfies the evaluation criteria. The
  test plan will also elaborate the various test
  activities and documentations needed for testing.
• Formal Technical Inspections
• Formal Technical Inspectors will do the
  inspection of the architectural design.

19
Work Breakdown

• Inception Phase (Phase 1 )
• Vision Document
• SQA Plan
• Project Plan
• Formal Checklist
• Phase 1 Presentation Date April 30th 2007

20
Work Breakdown(2)

• Elaboration Phase (Phase 2)
• Revise Vision Document
• Revise SQA Plan
• Revise Project Plan
• Develop Formal Requirement Specification
• Revise Architecture Design
• Develop Test Plan
• Formal Technical Inspection
• Develop Prototype
• Phase 2 Presentation Date June 1st 2007

21
Work Breakdown(3)

• Production Phase (Phase 3)
• Develop Code
• Testing
• Functional Testing
• Evaluate Test Result
• Documentation
• Write Test Report
• Write User Manual
• Final Presentation Preparation
• Phase 3 Presentation Date July5th 2007

22
Questions???