CMPT 370 Course Project

Library Information System Analysis and Design

Your Project TA

Where: CSIL MTF LabWhen : Monday 12:30-1:30

Wednesday 15:00-17:00 Friday 11:30-12:30 Or By appointment

Email: htw@sfu.ca

The Menu

IntroductionStake-HoldersAnalysis ComponentDesign Component Question and Answer

Introduction

Library is a repository of InformationThe information comes in a wide variety of

formatsThe library system is complexA perfect system does not exist Determine the most crucial componentsThe project is limited by the time available

The Information Pot

Paper based information: books, journals, magazine, newspaper, and maps

Multimedia based information: CDs, VHS, DVDs, LPs, Internet Connected Computers

A connected set of repositories

The Stake-Holders

UsersLibrariansLibrary AdministratorsOthers ?

The Users

Diverse group Varying

Expectations Way of thinking Experience Familiarity with library systems Circumstances

The library is build for the people that uses them, and so must the system we’re building.

The Librarians

Knowledgeable professional Sub-Pools handled by one librarianHelpers for usersManages the information pool.Knows the intricate details of the library

Library Administrator

Decision maker Sometimes Librarians take on this roleMake book purchases Can be the central authority of all

branchesHigh level view

What are we doing?

The ultimate goal Satisfy all the stake-holders to within some

reasonable limits (Making tradeoffs). Ensure the software is maintainable,

upgradeable, and extensible

Find out what is necessary (Analysis)Turn it into something you can implement

(Design)

The Menu

IntroductionStake-HoldersAnalysis ComponentDesign Component Question and Answer

Analysis

A.K.A Requirements gatheringInterview all the stake holdersObserve the current processPut the observation into a model

Analysis (What To Do)

Model the domain (as-is:to-be) Domain models should be simple but… Document the functional requirement

using use-case and use-case diagramsDocument the vocabulary used within the

domain Domain model will help you limit the scope

of the project

Analysis

Complete capture of the domain is essential

Look for Implicit requirementsA thoughtful model is required CRC method is recommended

The Menu

IntroductionStake-HoldersAnalysis ComponentDesign Component Question and Answer

Design (Putting Your Analysis to Work)

Translating the domain model into models that developers can understand.

Tools of the trade: Use-Cases( Which you should have done) Class Diagrams State Diagrams Interaction Diagrams Activity Diagrams, Component Diagrams Architecture Diagrams

Make use of any of the tools needed

Design

One step before implementationDetailed design is necessary for a

completely new system However re-use of pre-existing

implementation can possible reduce the design granularity

The design documents must clearly reflect what the implementation will look like.

Design

Remember the goal of the systemTime is the biggest issue.

The Menu

IntroductionStake-HoldersAnalysis ComponentDesign Component Question and Answer