Monday, 20 April 2015
On 10th April we sharted working on the
1.0 SYSTEM ARCHITECTURE
1.0 SYSTEM ARCHITECTURE
The
System Architecture is a way to give the overall view of a system and to place
it into context with external systems.
This allows the reader and user of the document to orient them to the
design and see a summary before proceeding into the details of the design.
1.1 Architectural Design
The
design below does not include all the components in the architecture. The
figure 2.1 depicts the overall EDT architecture, with highlighting components
that were built and deployed for EDT demonstration.
1.1.1 High Level Architecture:
1.0 Decomposition Description
Wednesday, 1 April 2015
The Design Document for An Enterprise Data Tracking System
The Design Document
1
Introduction
The
Software Design Document is a document to provide documentation which will be
used to aid in software development by providing the details for how the
software should be built. Within the
Software Design Document are narrative and graphical documentation of the software
design for the project including activity diagrams, collaboration models,
object behavior models, and other supporting requirement information?
1.1 Purpose
The
purpose of the Software Design Document is to provide a description of the
design of a system fully enough to allow for software development to proceed
with an understanding of what is to be built and how it is expected to build. The Software Design Document provides
information necessary to provide description of the details for the software
and system to be built.
1.2 Scope
This
Software Design Document is for a base level system which will work as a proof
of concept for the use of building a system that provides a base level of
functionality to fulfill the communication
improvement from field offices to main office and vice versa. This Software Design is focused on the base level
system and critical parts of the system.
For this particular Software Design Document, the focus is placed on aiding
management in enterprise resource planning. The system will be used in
conjunction with other pre-existing systems and will consist largely of a field
interaction of office workers and management of daily activities handled.
1.3 Overview
The
software design document is divided into eight (8) sections with various
subsections. The sections of the document are:
1:
Introduction
2:
System Overview
3:
System Architecture
4:
Data Design
5:
Component Design
6:
Human Interface Design
7:
Requirement Matrix
8:
Appendix
2.0 SYSTEM OVERVIEW
Give a
general description of the functionality,
context and design of your project.
Provide any background information if necessary.
The company is
finding problems in tracking most of the field activities done by the project
managers, field supervisors (Foremen) and the procurement department so this
lead to an Enterprise Data Tracking system that will enable this departments
communicate to each other and to the CEO himself can be able to view the
activities on ground and be able to comment and advice accordingly.
Use
Case understanding of the requirements of the system.
Use-Case
Model Survey
2.1
Actors
2.1.1 IT Specialist.
The
Data Manager is a user who creates accounts and issues flexible passwords and
usernames to various stuffs working with the Company.
2.1.2 Project Managers
Monitor
project phases.
Fleet
conditions (Tracks repairs and services).
Presents
operation costs (pay roles, petty cash) to the finance department.
Presents
wealth and safety of workers to the top management (CEO).
Presents
progress reports to the technical manager (HRM).
Presents
environmental impacts to the technical manager (HRM).
Settles
social relationships among the workers (interpersonal issues among the workers
beyond settlement by the field supervisor (Foreman)) he then makes a final
judgment on that particular worker whether to discontinue him or leave him to
continue working in a certain field.
Presents
inventory and stock take (tools, equipment’s, and materials used, material
balance) to the procurement officer.
2.1.3 Foremen (Field supervisors)
The
foremen or field supervisors account for the materials used.
Monitor
attendance of the workers at the field.
Settle
issues among the workers and writes recommendation to the worker and presents
it to the project manager.
Prepares
a time sheet in which a pay role is extracted.
Takes
photos of the field activities and forwards them to the CEO
2.1.4
Procurement Manager
The
procurement manager writes a loading instruction.
Does
delivery note (weigh bill).
2.1.4 CEO
The
Chief Executive Officer interacts with the system by advicing the procurement
manager on which action to take after a project manager sending material
request sheet.
The
CEO also comments on the activates done by the project manager.
2.1.5 Drivers
They
deliver materials at the sites.
Report
on fleet coditions
2.2 List of Use Cases
2.2.1 IT Specialist
2.2.1.1
createUserAccount
2.2.2 Project Managers
2.2.2.1
monitorProjectPhase
2.2.2.2
checkFleetCondition
2.2.2.3
sendOperationCost
2.2.2.4
checkWealth
2.2.2.5
sendProgressReport
2.2.2.6
sendEnviroImpact
2.2.2.7
makeJudgement
2.2.2.8
sendStockTake
2.2.3 Foreman (Field Supervisor)
2.2.3.1
accountForMaterial
2.2.3.2 monitorAttendance
2.2.3.3 writeRecommendation
2.2.3.4 prepareTimeSheet.
2.2.3.4 takePhoto
2.2.4 Procurement Manager
2.2.4.1
writeLoadInstruction
2.2.4.2 writeDeliveriveryNote
2.2.5 CEO
2.2.5.1
makeAdvice
2.2.5.2 receiveCapturedImage
2.2.5.3 writeComment
2.2.5 Driver
2.2.5.1
makeDelivery
2.2.5.2 reportFleetCondition
2.3 Use Case Diagrams
2.3.1 IT Specialist-
Essential Use Cases (“creates accounts and issues flexible passwords and
usernames to various stuffs working with the Company.” for future Logins)
Subscribe to:
Comments (Atom)