SENG 205 Project Outline, T2 2020

Assessment-1 Initial Design, Plans and justification

Student ID Team member name Task performed

K191243 Vinay Sehdev Introduction

K190350 Kajal Sarwara Various methodologies used in

Software development

K190722 Sakushal Sethi Nonfunctional requirements

K190745 Anita Karki Functional-requirements,

Preliminary budget

K191318 Vamsi Krishna Madala Architecture and testing

1
Table of contents:

Introduction:...............................................................................................................................................3
 Purpose:.....................................................................................................................................3
 Document Conventions:............................................................................................................3
 Intended Audience and reading suggestions:...........................................................................3
 Project Scope..............................................................................................................................3
 Description and Priority.............................................................................................................3
Various methodologies used for software development processes:.........................................................4
 The waterfall model:..................................................................................................................4
 Incremental model:....................................................................................................................4
 The spiral model:.......................................................................................................................4
 The Agile model.........................................................................................................................4
The model used in this project:..................................................................................................................5
 Functional Requirements:..........................................................................................................5
 Non-functional Requirements:..................................................................................................6
Architecture:...............................................................................................................................................6
 Testing:.......................................................................................................................................7
 Automated Unit testing and Test Driven Development (TDD):................................................7
 Preliminary Budget:...................................................................................................................7
References:.................................................................................................................................................7

2
Introduction:
 Purpose: Wakanda Institute of Technology and Sciences (WITS) has decided to start providing
online lectures to students all over the world as part of its global outreach program. In order to
achieve this, they have decided to develop their own online live video-based lecture delivery
tool: Wakanda Institute Live Streaming System (WILSS). The purpose of WILSS is to build an
online system to manage students and lecturers to ease learning and access their registered
courses and teaching remotely in their desired time. It helps students learn better to understand
the concept on their own. Students watch video lectures and learn independently.

 Document Conventions:
The following are the list of conventions used in this document.
Student: A general login is and password is given to the student to watch the online videos and
tutorials 
Professor: A general login is and password is given to the professor to teach the students and
clarify the doubts if any.
Admin: An admin is used to reset and update new password. He is also responsible for the
updating of security features and system software.
Moreover the font used in the report is Calibri 12.It is used for the headings which are
highlighted with the BOLD font. The remaining parts of the report is written in Calibri font and
11 font size.

 Intended Audience and reading suggestions:

This project is a proof of concept for the online education system and it is restricted within the
college premises. The college professors and students and the admin who maintain the whole
system to draw insights are the only intended audience.

 Project Scope
Online education system can be applied in multiple ways like presenting
the educational content, and facilitating the education processes. WILSS can effectively operate
within both selected and intended integrated course design model.
 Description and Priority:
The online education system maintains the information of students, lecturers and their
attendance, enrolled courses, assignments and, mark-lists. It currently has high priority because
in the current system and in cases of future pandemics, it is difficult to travel to the premises. It

3
 not only reduces costs but also saves money and increases lecturer-student time and access to
expertise.

Various methodologies used for software development processes:

 The waterfall model: It was the primary Process Model to be announced. It is additionally
alluded to as a linear-sequential life cycle model. It is exceptionally easy to comprehend and
utilize. In this model, each stage must be finished before the following stage can start and there
is no coinciding in the stages.
 Waterfall Model – Design: The consecutive stages in Waterfall model are − Requirement
Gathering and investigation, System Design, Implementation, Integration and testing,
Deployment of framework and Maintenance. (Tutorial point)
 Incremental model: It is a procedure of programming advancement where prerequisites
are separated into various independent modules of programming improvement cycle. This
model is otherwise called Successive version model. There are two kinds of staged
delivery model and parallel development model.
 The different periods of the model are as per the following: Requirement investigation,
Designs and improvement, Testing and Implementation.( Java point)
 The spiral model: This model was created on the finish of the 1980s, it was laid out by
Barry Boehm, and presents something that different models didn't consider, which is risk
investigation. Basically, this model endeavors to unite key parts of some other noticeable
models trying to accumulate the most suitable qualities from each model.(B. Vivek ,2015).
 Spiral model design: Identification, Design, Construct or Build and Evaluation or risk
analysis. 
 The Agile model: Agile SDLC model is a mix of iterative and gradual procedure models
with center around process flexibility and consumer loyalty by fast conveyance of working
programming item. Spry Methods break the item into small incremental builds. These
builds are given in cycles. (Boehm, 1996)
 Agile model design :
I. Requirements gathering
II. Design the requirements
III. Construction/ iteration
IV. Testing/ Quality assurance

4
 V. Deployment
VI. Feedback. (B. Vivek ,2015).

 Advantages :
I. Adaptive to the evolving condition: In coordinated programming advancement
strategy, programming is created more than a few emphases. Every cycle is
described by examination, structure, and usage and testing. After every cycle the
little task is conveyed to the client for their utilization and input. Any progressions
that redesign the product are welcome from the client at any phase of
advancement and that changes are executed.
II. Ensures consumer loyalty: This procedure requires dynamic client inclusion all
through the Development. (Boehm, 1996). The expectations created after every
emphasis is given to the client for use and improvement is done dependent on
the client input as it were. So toward the end what we get as the last item is of
high caliber and it guarantees the consumer loyalty as the whole programming is
created dependent on the prerequisites taken from client.
III. Least documentation: The documentation in this technique is short and direct
however it relies upon the group. They don't make documentation on inner
design of the product.

The model used in this project: In this project we are using agile model. The model utilized in this
undertaking: In this task we are utilizing agile model. This technique requires less arrangements and
planning and it breaks the tasks into little parts. This technique is intended for momentary projects with
an exertion of group work that follows the product advancement life cycle. The contribution of
programming group the executives with clients diminishes the risks related with the product. This
coordinated procedure is an iterative procedure in which changes can be made by the consumer
satisfaction. In this procedure new highlights can be included effectively by utilizing different cycles.

High-Level Requirements:

Functional Requirements:
 Students who have pre-enrolled for the courses should have access to the lectures and no one
else should be able to view them.

5
  The lecturers should be able to capture attendance automatically and an option to override
manually should be provided as well. They should be able to apply their leaves effectively.
 Two UI’s one for lecturer and one for student have to be enabled. The lecturer has to be
provided with an ability to evaluate student’s assignments and view the completion of the
enrolled courses.
 Students should be able to communicate with other peers inside the organization within their
courses.

Non-functional Requirements:
 The communication between lecturers and students has to be secured.
 All the documents or data shared on the platform has to be encrypted. No personal or
organizational data has to be exposed.
 The login portal for lecturers and students has to be different to maintain granularity.
 The attendance management system has to be enabled without any glitches providing no
chance for proxy.

Architecture:

Fig-1 Architecture of
the system

As per the project

design, the
student/lecturer will
first login to the
WILSS portal.

6
Considering the use-case to be a student, attendance will be captured along with the time of login. If the
student wants to start a video conference, he will add the desired people and can record and share it if
he wishes to. If he just wants to send a message, he can add the people he wants to address to and also
mark people in carbon copy and send it and logout of the portal.

Testing:

Automated Unit testing and Test Driven Development (TDD):

Every unit of project cannot be tested manually. We prepare a few test-cases manually and run a script
to ensure all the test-cases are passed when the unit of project is executed. Corrections are made
according to the errors faced in passing the test cases. This helps the project finish smoothly in micro-
agile way which addresses the expected behavior and the optimal structure of the code.

Preliminary Budget: This section provides an initial budget for the project, itemized by cost factor.
Based upon the report the preliminary budget will be around 1000$ in order to get the software
designing tools, Agile methodology software’s. This is only the estimated budget and it can vary
depending upon the further requirements.

References:
1) Boehm, “ Anchoring the Software Process,” IEEE Software, July 1996,” retrieved
from :https://pdfs.semanticscholar.org/ee87/e706bb222fce5ca900976afc2d674ad43034.pdf
2) B. Boehm and D.Port,”Balancing Discipline and Flexibility with the Spiral Model and MBASE”.
Crosstalk, Dec. 2001. Retrieved
from :https://www.researchgate.net/publication/250888533_Balancing_Plan-
Driven_and_Agile_Methods_in_Software_Engineering_Project_Courses
3) Tutorial points, SDLC waterfall model ,retrieved
from https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm
4) Java point ,increment model, its various phases, advantages and disadvantages”, retrieved
from :https://www.javatpoint.com/software-engineering-incremental-model
5) Bhatnagar, Vivek. (2015). A comprative study of sdlc model. IJAIEM. 4. 23-29. Retrieved
from :https://www.researchgate.net/publication/305863548_A_comprative_study_of_sdlc_model