Wakanda Institute

Live Streaming
8/16/2020

System
Initial Design, Plans and Justification

SUBMITTED BY SUBMITTED TO,

NIRANJAN MAGAR (K200153) DR. MANZUR ASHRAF
ANIK KOIRALA (K191101)
SABINA CHAPAGAIN (K190140)
ANIL THAPA (K191090)
SONY THA (K190217)
TABLE OF CONTENTS
1. Executive Summary
2. Introduction
3. Body
 Initial Project Information
 New System Design and Description
 System Requirements
 System Development Methodologies
 Project Timeline
 Estimated Cost Table/ Preliminary Budget Breakdown
- Estimated Cost Table, Threats, Risks and Security Management
4. Conclusion

References

1. EXECUTIVE SUMMARY
The major focus of this report includes the initial design, plans and justification of our project
consisting of various methodologies for software development processes, appropriate
development method for a complex problem and lastly design, specification, and requirement
which are the base of our project.

2. INTRODUCTION
The report consists of initial design of the project also referred as Wakanda Institute Live
Streaming System (WILSS) which reflects its plan and justification for delivering online live video-
based lecture and further divided into sub-class which are initial project information, new
system design, system requirements and methods, project timeline and lastly budget breakdown
giving clear overview of the project.

3. BODY

 INITIAL PROJECT INFORMATION

The main target of our project is to develop online live video-based lecture delivery tool:
Wakanda Institute Live Streaming System (WILSS) for our client, Wakanda Institute of
Technology and Sciences (WITS). We promised to facilitate the system with basic
requirements and some other elicit requirement that could be supported by budget and
political environment of Wakanda Institute. Particularly in this project we will be using agile
development methodology for developing software. If we can work as per our plan,
hopefully we will succeed and we make sure to face any risk that may arise in processes.
 NEW SYSTEM DESIGN AND DESCRIPTION
High requirement can be elicited by analysing the step to step use case model. People,
product and system are the capable actors in this case. We are working for developing
application that connects lecturer with student in live video. The system is to be developed
with two interfaces: one for student and next for lecturer. This system should access verbal
exchange between lecturer and enrolled students. WILSS should accessed lecturer to record
attendance of students automatically whenever they make live communication. The system
should have capability to block the students who enrolled in incorrect course for attending
lecture. Besides all these high requirements, some other requirements can be added which
makes this system even more effective (Wolf, M., 2012).

These elicit requirements can be removed in future if in case our budget and
political climate support. Lecturer shall record their live lecture for future purpose. Both
administrator and student must be able to edit, remove and update their personal detail
from registered account. Whenever students join the platform, it should automatically send
four-digit codes to student email for privacy purpose.

 SYSTEM REQUIREMENT (Classifying and prioritising the high-level

requirement)
For the software project, business and management perceptions and goals are need to seek
out. First, business opportunity and business needs need to be fulfilled to classify the high-
level requirement. The project which needs to be launched should be justified by individual
functionality to fulfil the requirement. Business flow should be managed so that it meets the
level of requirement with good relation of system and interface. Data, formats, and
information needs to be implemented to prioritize the high-level requirement. Other
constraints like performance, reliability, user interface and security should be balanced. The
requirements should be categorized and prioritized for the high-level requirement.

The stakeholders and their viewpoints of the requirement should be identified. The
identified viewpoint of the requirement should be refined and categorized to eliminate the
duplication (Shameem, p389-401, 2020). Time, resources and technical capabilities should
be managed so that the requirements will be met. Data and information should be
formulated as per the requirements and needs for the project management. The
requirements should be formulated with the help of different stakeholder.
  SYSTEM DEVELOPMENT METHODOLOGIES
Agile software improvement additionally alluded to just as Agile is a sort of advancement
methodology that foresees the requirement for adaptability and applies a degree of realism
to the conveyance of the completed item. Agile software advancement requires a social
move in numerous organizations since it centres around the spotless conveyance of
individual pieces or parts of the software and not on the whole application (Harb, Sarnikar,
S., 2015).

It is also a utilized to design a taught software the board

procedure which additionally permits some regular change in the development project. This
methodology is very suitable for every purpose because it is safe and secure because
without authority of main person no one can access as well as to access on it. They must
pass through different password more important the main member like lecture has full
access toward the student portal so he can check at any time.

Fig: - agile software development methodology

As we can see we can use lots of software development methodology like

Waterfall Model, Rapid Application Development (RAD), Spiral Model, etc. as compare to all of them
we found this one more reliable because it is simple and less risk and good result. As well as Agile
philosophy has a versatile methodology which can react to the changing prerequisites of the
students and lecture just as immediate correspondence and consistent input from student and
lecture delegate leave no space for any mystery in the framework (Misra, U., 2009).
 PROJECT TIMELINE/SCHEDULE

Project scheduling is a very important tool used for project planning and developing. A good
project timeline offers some trust on your work to maintain your project on the right path as
well as carryout the project and predicts to finish the work on completion date. The
following table picture explain schedule of our project:
 Fig: project timeline in Gantt chart

 ESTIMATED COST TABLE/ PRELIMINARY BUDGET BREAKDOWN

A Budget breakdown is a tool used by a project manager to estimate the total amount of
cost spend on a project. For the proper utilization of budget, we divided our tasks and total
cost required for each task. And below listed is the budget breakdown table.
 4. Conclusion

In a nutshell, this report illustrates the initial design of the Wakanda Institute Live Streaming
System (WILSS) as requested by the client Wakanda Institute of Technology and Science
(WITS) where basic requirements, methodology and timeline and budget breakdown are
clearly classified and described which are the pillars for the project development.

References:
Wolf, M., 2012. Computers as components: principles of embedded computing system design.
Elsevier.

Misra, S.C., Kumar, V. and Kumar, U., 2009. Identifying some important success factors in adopting
agile software development practices. Journal of Systems and Software, 82(11), pp.1869-1890.

Harb, Y., Noteboom, C. and Sarnikar, S., 2015. Evaluating project characteristics for selecting the
best-fit agile software development methodology: a teaching case. Journal of the Midwest
Association for information Systems, 1(1), pp.33-52.

Shameem, Mohammad; Khan, Arif Ali; Hasan, Md. Gulzarul; Akbar, Muhammad Azeem. IET
Software. 2020, Vol. 14 Issue 4, p389-401. 13p. DOI: 10.1049/iet-sen.2019.0196.