Design Specification Report for Project Management Information System

This assignment presents a detailed design specification report for a Project Management Information System (PMIS). It begins with a literature review of ICT requirements for project management, followed by an analysis of an organization's business processes. Based on this analysis, the report proposes the design and development of a new web-based project management tool or portal, justifying the chosen solution. The functional requirements include document management, drawing management, meeting management, quality management, photo documentation, contract and claim management, procedural support, and a construction diary. Key Performance Indicators (KPIs) and metrics are defined to assess the system's performance, including critical issues, correction rates, risk occurrence, and change management. Business continuity planning, encompassing high availability and disaster recovery, is also addressed, highlighting the use of a single configuration database, load balancing, real-time synchronization, and automated security tools. The system development utilizes the Waterfall model, with three phases: Vision, Pilot Implementation Framework, and Replicate & Extend. The report also includes a system test plan which describes the testing strategy and approach to verify that the application meets the established requirements of the business prior to release.

PMIS
Part 2

Workflow
 Integration of modules
 Needs management
 Requirements management module
 Financial system
 Cost & budget management
 Resource management
 Management portal
 Report handling module
 All of these modules will be synced with the data
exchange functionality and these will be further
synced with finances, labour, and operations.

Functional Requirements
 Inclusion of the documents management system in
order to handle the tasks, meeting, workflows, and
portfolios.
 Ability to carry out drawing management covering plan
code management, automated index management,
Automated planning of the delivery lists, and handling
of the workflows.
 Ability to manage the minutes of meeting covering
automated tracking of the tasks, development and
follow-up of the protocols.
 Ability to make sure that quality management is
included as an essential functionality.

Functional Requirements
 Photo documentation covering easy photo
upload, key-wording, and organized view
shall be included.
 Contract and claim management shall be
included as a functionality that shall cover
cost trend analysis, risk handling, and cost
monitoring.
 Procedural support must be included land
acquisition catalogue, statements,
objections, and topic catalogue.

Functional Requirements
 Construction diary must be included as
system functionality.
 The general functions, such as full-text
search, reporting, workflow
management, and OCR shall be
included.

KPIs & Metrics
 Critical issues per product or per phase
shall be determined
 Calculation of the corrections made in the
requirements and specifications document
during the review process
 Rate of risk occurrence
 Number of open bugs or defects
 Number of changes requested and
changes approved

Business Continuity
planning – High Availability
 There shall be a single configuration database that
must be used.
 The application servers shall have load balancing as
the essential requirement.
 The synchronization between the servers shall be
maintained on the basis of the storage technologies
and real-time synchronization must be made possible.
 There shall be protection from the database server
and application server provided and ensured at all
times.
 The single points of failure must not be present.

Business Continuity planning
– Disaster Recovery
 There shall be a separate configuration
database present for the secondary data
centre.
 Recovery point objectives shall be defined
and the data backups shall be auto
scheduled on the basis of the same.
 The use of automated security tools and
protocols shall also be done so that the
disaster recovery activities can be carried
out.

System Development using
SDLC Approach
 Use of Waterfall model as the SDLC
approach
 Three phases in the development
process
 Phase 1: Vision
 Phase 2: Pilot Implementation Framework
 Phase 3: Replicate & Extend