Piazza Promotion P.L.
C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Inception Report for [Link]
PIAZZA COMMUNICATION
Revision History
Piazza Communication Page 1 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Date Version Description Author
24/Aug/2022 1.0 Initial draft for feedback Natnael Zeleke
25/Aug/2022 1.1 Updated with feedback at end of E1 Biniyam Ashbir
Piazza Communication Page 2 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Overview
2. Project Overview
2.1 Project Purpose, Scope, and Objectives
2.2 Project Deliverables
3. Project Organization
3.1 Organizational Structure
3.2 Roles and Responsibilities
4. Management Process
4.1 Project Plan
4.1.1 Phase Plan
4.1.2 Iteration Objectives
4.2 Project Monitoring and Control
4.2.1 Requirements Management Plan
4.2.2 Schedule Control Plan
4.2.3 Quality Control Plan
Piazza Communication Page 3 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Software Development Plan
1. Introduction
1.1 Purpose
This Software Development Plan will define activities for maintenance and integration of
new features on Yegara Portal of MoLS, (Major improvements on technology &
functions of the portal to be carried out as per the scope of work mentioned on the TOR.
1.2 Overview
This document contains the following information:
Project Overview - provides a description of the project's purpose, scope and objectives.
It also defines the artifacts that the project is expected to produce.
Project Organization - describes the organizational structure of the project team.
Management Process - defines the major phases and milestones for the project, and
describes how the project will be monitored.
Technical Process Plans - provides an overview of the software development process,
including methods, tools and techniques to be followed.
Supporting Process Plans - this includes the configuration management plan.
2. Project Overview
2.1 Project Purpose, Scope, and Objectives
The primary goal of this project is to allow team members to learn how to follow a
software development process to construct software. A secondary, but still important,
goal is to construct an Alpha-quality version of an application that can be transitioned for
future development.
2.2 Project Deliverables
The following deliverables will be produced during the project:
Piazza Communication Page 4 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
• Verification and due diligence facilitation
• Collect legal documents required from investors
• Activate the account of trusted and verified investors to access the web and mobile
application
• Collect and store the legal documents of investors on a secure local server
• Follow up if start-ups have all the required information included on their profile
before getting activated
• Activate start-ups providing the required information based on the template
provided. I.e. the current system provides a start-up pitch presentation template
for start-ups.
• Backup the legal documents collected from investors weekly
• IT system and maintenance
• Hosting
• Monitor and maintenance of the current system
• Providing technical support for the ministry of labor and skill works to access
the administrator account
• Setup instant support center for startups and investors where they can get
support through email or a phone call
• Develop a system manual and documentation Report the vulnerability
assessment of the web and mobile application quarterly
• Develop a plan and relevant manuals for MoLS staff training, change
management, and capacity building within MoLS on the system,
• Providing the complete source code of the portal to MoLS. The ownership
rights of the source code will remain with MoLS
• Providing support and maintenance activities for a period of 1 year
• Design a system to log errors Answer user questions
3. Project Organization
3.1 Organizational Structure
Role Names
Piazza Communication Page 5 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Project Manager Mulualem Mebratu
System Architect Natnael Zeleke
System Analyst Biruk Mesfin
Requirements Specifier Zekariyas sebsebe
Requirements Reviewer Zekariyas sebsebe
Designer Natnael Zeleke
Code Reviewer Samuel Alemayehu
Tester Binyam Paulos
Configuration Management Biruk Mesfin
Manager
User Interface Designer Alex Solomon
Tool Specialist Alex Solomon
Web Site Administrator Biruk Mesfin
3.2 Roles and Responsibilities
The responsibility of our team members is defined by the Rational Unified Process with
the exception of the Implementer-Integrator and Recorder.
Role Description
Project Manager Allocates resources, shapes priorities, coordinates interactions
with the customers and users and generally tries to keep the
project team focused on the right goal. The project manager
establishes a set of practices to ensure the integrity and quality of
project artifacts.
Piazza Communication Page 6 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
System Architect Leads and coordinates technical activities and artifacts
throughout the project. The architect establishes the overall
structure for each architectural view: the decomposition of the
view, the grouping of elements and the interfaces between these
major groupings.
System Analyst Leads and coordinates requirements elicitation and usecase
modeling by outlining the system’s functionality and delimiting
the system.
Requirements Specifier Details the specification of a part of the system's functionality by
describing the Requirements aspect of one or several use cases
and other supporting software requirements. The requirements
specifier may also be responsible for a use-case package, and
maintains the integrity of that package.
Requirements Reviewer The requirements reviewer plans and conducts the formal review
of the use-case model.
Architecture Reviewer The architecture reviewer role plans and conducts the formal
reviews of the software architecture in general.
Designer Defines the responsibilities, operations, attributes, and
relationships of one or several classes, and determines how they
will be adjusted to the implementation environment. In addition,
the designer role may have responsibility for one or more design
packages, or design subsystems, including any classes owned by
the packages or subsystems.
Implementer-Integrator Responsible for developing and testing components, in
accordance with the projects adopted standards. Additionally,
the Implementer-Integrator integrates components into the
system.
Code Reviewer Ensures the quality of the source code, and plans and conducts
source code reviews. The code reviewer is responsible for any
review feedback that recommends necessary rework.
Tester Responsible for the core activities of the test effort, which
involves conducting the necessary tests and logging the
outcomes of that testing.
Configuration Management Manager Provides the overall Configuration Management (CM)
infrastructure and environment to the product development team.
The CM function supports the product development activity so
that developers and integrators have appropriate workspaces to
build and test their work, and so that all artifacts are available for
inclusion in the deployment unit as required. The configuration
manager also has to ensure that the CM environment facilitates
product review, and change and Responsible for the core
activities of the test effort, which involves conducting the
necessary tests and logging the outcomes of that testing.
Piazza Communication Page 7 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
defect tracking activities. The configuration manager is also
responsible for writing the CM Plan and reporting progress
statistics based on change requests.
User Interface Designer Leads and coordinates the prototyping and design of the user
interface.
Tool Specialist Responsible for the supporting tools on the project. This includes
selecting and acquiring tools. The tool specialist also configures
and sets up the tools, and verifies that the tools work.
Web Site Administrator Responsible for maintaining the project web site, which contains
project news, general project information and project
documentation.
Recorder Responsible for writing a “Meeting Minutes” document after
each team-wide meeting and making it available to all team
members.
4. Management Process
4.1 Project Plan
4.1.1 Phase Plan
The development of the system will be conducted using agile software
development approach where multiple iterations occur within a phase. The phases
and the relative timeline is shown in the table below:
Phase # of Iterations Start End
Inception Phase 2 26/Aug/22 28/ Aug /22
Consultation Phase (Detail 1 28/ Aug /22 29/ Aug /22
Requirement Consultation)
Piazza Communication Page 8 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Elaboration Phase 2 29/ Aug /22 31/ Aug /22
Construction Phase (Design 3 01/Sep/22 02/Sep/22
of SRS and SDS)
User manual preparation 1 03/Sep/22 06/Sep/22
It System support and 4 24/Aug/22 24/Aug/23
maintenance
End user and 1 15/Sep/22 16/Sep/23
administration training
The table below describes each phase and the major milestone that marks the completion of the
phase.
Phase Description Milestone
Piazza Communication Page 9 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Inception Phase The Inception Phase will The Lifecycle Objectives
develop the product Milestone at the end of the phase
requirements and establish the marks the completion of
business case for the system. Requirements Definition and
The major use cases will be System Function
developed as well as the high Scoping.
level Software
Development Plan.
Elaboration Phase The Elaboration Phase will The Lifecycle Architecture
analyze the requirements and Milestone at the end of the phase
will develop the architectural marks the completion of the
prototype. At the completion architecture design and skeleton
of the Elaboration Phase, all implementation, and definition of
use cases selected for Release all use cases.
1.0 will have completed
analysis and design. The
architectural skeleton will test
the adequacy of the
architecture for Release 1.0.
Construction Phase During the Construction The Initial Operational
Phase, remaining use cases Capability Milestone at the end of
will be analyzed and the phase marks the release of an
designed. The implementation Alpha version of the system.
and test activities to support
the R1.0a release will be
completed.
Transition Phase The Transition Phase will The 1.0a Release Milestone at the
prepare the 1.0a release. end of the phase marks the release
of a packaged Alpha version of the
system.
4.1.2 Iteration Objectives
Phase Iteration Description Associated Risks
Milestones Addressed
Piazza Communication Page 10 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
Inception Phase I1 Defines initial product none Develops initial
requirements and requirements
Software Development documents for
Plan. review.
I2 Defines product Lifecycle Develops realistic
requirements and
Software Development Objectives Software
Plan.
Milestone Development
Plans and scope.
Elaboration E1 Complete analysis and Architecture can
design for major use cases. be reviewed.
Phase Complete initial design of
architecture.
High-risk use
cases can be
reviewed.
E2 Complete analysis and Architectural Architectural
design for all use cases. issues clarified.
Complete prototype of Prototype
architecture.
Technical risks
mitigated.
Construction C1 Implement skeleton of R0.1 Software Architecture
architecture. available for
Phase implementers.
C2 Implement and test high-risk R0.5 Software High-risk use
use cases cases are
implemented.
Piazza Communication Page 11 of 12
Piazza Promotion P.L.C
Bole Subcity
Addis Ababa, Ethiopia
Email: connect@[Link]
Tel: 090 977 4515
Website: [Link]
C3 – Implement and test low-risk R1.0a Software Defects
Develop use cases. Complete alpha minimized.
testing.
Alpha
release
Transition Phase T1 Package R1.0a Software for R1.0a Software Usable system
distribution. release.
4.2 Project Monitoring and Control
4.2.1 Requirements Management Plan
The Project manager will continually check if the project is aligned perfectly with the
requirements and deliverables mentioned on objective 2.2 (Project Deliverable). If there
are any minor modification from additional consultation after/while the construction
phase, the project manager will include them with the project deliverables as mentioned
on objective 2.2.
4.2.2 Schedule Control Plan
The project manager will maintain a summary schedule showing the expected date of
each milestone. Every week, using the weekly team meeting, the project manager will
reevaluate the progress of the project, to determine whether the project is on schedule.
If the project is not on schedule, the project manager will consult with team members to
determine corrective action, which may result in updating the schedule and/or increase
human resource capital working on the project to complete the project on time.
4.2.3 Quality Control Plan
All deliverables are required to go through the appropriate review process. The review is
required to ensure that each deliverable is of acceptable quality, using our internal system
guidelines.
Piazza Communication Page 12 of 12
