Desklib - Online Library for Study Material with Solved Assignments, Essays, Dissertation

This portfolio assessment includes ER diagrams, use case diagrams, work breakdown structure, and testing plan for various systems. It also covers the six core processes of SDLC. The content is related to courses like SBM4201 System Analysis and Design and includes references for further reading.

Portfolio Assessment
SBM4201 System Analysis and Design
[Student name]
[Student roll no]

Table of Contents
Portfolio 1.........................................................................................................................2
Portfolio 2.........................................................................................................................6
Portfolio 3.........................................................................................................................7
Portfolio 4..........................................................................................................................8
Six Core Processes of SDLC.......................................................................................................8
Project Initiation.............................................................................................................................................8
Planning & Requirements Analysis................................................................................................................8
Design & Development..................................................................................................................................8
Testing & Implementation..............................................................................................................................9
System Deployment & Closure......................................................................................................................9
Maintenance & Support..................................................................................................................................9
Portfolio 5........................................................................................................................12
References.......................................................................................................................14
1

Portfolio 1
Entities – Following are key entities and their attributes of the proposed student registration
system:
Entity name Attribute
Program programName
programDuration
programStartDate
programFinishDate
Student studentID
studentName
studentAge
studentPhoneNo
studentEmail
Course courseID
courseName
courseStartDate
courserFinishDate
programName
Employee employeeID
SSN
employeeName
employeeAddress
employeePhoneNo
employeeEmail
Desgination
accessPriviledge
Payment paymentID
paymentDate
paymentAmount
PaymentMode
StudentID
programName
courserID
2

Use case diagram
3

Entities – Following are key entities and their attributes of the proposed Sydney dentist
management system:
Entity name Attribute
Employee employeeID
SSN
employeeName
employeeAddress
employeePhoneNo
employeeEmail
Desgination
accessPriviledge
Patient patientID
patientName
patientAddress
patientPhoneNo
patientEmail
medicalHistory
Appointment appointmentID
appointmentDateTime
doctorID
patientID
bookedByEmpID
reminderDate
Doctor doctorID
doctorName
doctorSpeciality
Experience
4

Use case diagram
5

Portfolio 2
ER diagram
6

Portfolio 3
Work Breakdown Structure
WBS Task Name Duration Predecessors
1 system design 5 days
2 subsystem A design 5 days 1
3 subsystem B design 4 days 2
4 subsystem C design 5 days 3
5 Program A 9 days 4
6 program B 5 days 4
7 program C 8 days 4
8 Testing 4 days 5,6,7
Critical path
WBS Task Start Date End Date EST EFT LST LFT Slack
1 system design 14-09-2018 19/09/18 0 5 0 5 0
2 subsystem A design 19/09/18 24/09/18 5 10 5 10 0
3 subsystem B design 24/09/18 28/09/18 10 14 10 14 0
4 subsystem C design 28/09/18 03/10/18 14 19 14 19 0
5 Program A 03/10/18 12/10/18 19 28 18 28 0
6 program B 03/10/18 08/10/18 19 24 22 28 4
7 program C 03/10/18 11/10/18 19 27 19 28 1
8 Testing 11/10/18 15/10/18 28 32 28 32 0
All those activities which are having 0 slack, form the critical path i.e. 1 > 2 > 3> 4 > 5 > 8
Work Breakdown Structure
Task Name Duration Predecessor
1 Research 15
2 understanding system requirements 14 1
3 writing algorithms and coding 20 2
4 Debugging and testing 8 3
5 deploying and maintained 5 4
Critical path
Task Name Start Date Finish Date EST EFT LST LFT Slack
1 Research 14-09-2018 29-09-2018 0 15 0 15 0
2 understanding system requirements 29-09-2018 13-10-2018 15 29 15 29 0
3 writing algorithms and coding 13-10-2018 02-11-2018 29 49 29 49 0
4 Debugging and testing 02-11-2018 10-11-2018 49 57 49 57 0
5 deploying and maintained 10-11-2018 15-11-2018 57 62 57 62 0
All those activities which are having 0 slack, form the critical path i.e. 1 > 2 > 3 > 4 > 5
7

Portfolio 4
Six Core Processes of SDLC
Project Initiation
The kick-off meeting would be executed within the team members of the team at CarHire.
The overall estimation of the project has been put up at 1 year and 2 months by the IT
department. Some key areas as well as requirements would be highlighted based on business
case as well as feasibility process would be carried out. In this feasibility analysis process, it
will be based on operational, economic, technical and environmental factors. All results from
these studies would then be compiled and analyzed in Project charter. This document would
include details such as the project highlights, key areas of the project and feasibility studies
(Cohen, Dori & De Haan, 2010).
Planning & Requirements Analysis
The requirement and planning analysis phase would include various fact finding methods as
well as their execution as the very first. These techniques would thereby include various
interviews that will be conducted with CarHire members including customer, employees,
development team, etc. Some other methods that would be deployed will include domain
analysis, group discussions, observations as well as brainstorming. The entire data that will
be collected in this process will then be analyzed in order to ascertain both non-functional
and functional needs of the system. After this, the planning activities will be done which will
include the scope management plan, installation plan of servers, databases and systems.
Among these, the budget estimations as well as schedule estimations would also be
conducted. Communication planning, Risk Planning as well as Quality management would
be based on the resources which will then be distributed to project-based activities (Singh &
Sharma, 2015). Afterwards, a project plan would be developed.
Design & Development
The mobile application would need to be designing by making use of modern responsive
design principles. Also, the mockups for each of such systems would also be prepared by
making use of platforms and tools for the system. A compatibility analysis study will also be
done and further ahead the source-code for each of these systems shall be developed. The
network and database diagram would be done using the front-end systems and then the
system would be released to the team to test it.
8

Testing & Implementation
The system which would be made by the development team would then be tested as well as
executed for various activities including integration, security and performance testing. The
overall system reviews as well as inspection of all the project activities will be executed too.
There might be certain alterations that may be needed in the system and these could very well
include resolution of the defects, modification and addition of all the functionality among
others. Any changes that needs to be incorporated at this stage shall be done with the help of
a proper change planning process and the final defect report would be sent to the PM or the
Project Manager (Larim, Albuolayan, Sabaa & Rehman, 2016).
System Deployment & Closure
An ultimate review would then be carried out for the system by technical experts. There
needs to be system documentation prepared for both the learning systems. These
documentations would also include tutorials, manual, system description, guides and FAQs.
The ultimate users of the system which includes faculty members, staff, administration and
users would be provided with adequate training. Lastly, the project deliverables would need
to be signed off by each of the stake holders and the final system shall be delivered to the
end-users (Kaur, 2015).
Maintenance & Support
There needs to be appropriate amount of maintenance support provided by the company in
the form of system updates, patches and maintenance activities. Furthermore, online, on-call
and remote assistance shall also be provided for the system whenever users may face
problems in the form of security issues, system errors and operational issues. Such issues
shall also be recorded, followed-up and resolved at the earliest. Finally, a log of all of the
activities that took place shall be recorded.
9

WBS
The car rental service includes following use cases:
 Register for rental
 Make payment
 Cancel rental booking
 Update rental booking
 Create booking
 Generate reports
 Send reminders
 Send notifications
10

Use case diagram
11

Portfolio 5
The test plan is based on bottom-up testing approach and will have following testing phases:
Phase Person Description
Unit Test Developers It will test migrated database in an isolated
environment.
Integration Test Developers Different modules of database are tested together.
Performance
Test
Testing team In this entire testing is done independent of user
interaction.
Acceptance
Test
Testing Team The database shall be tested from the perspective of end
user.
Testing should be done before and after migration. The different phases of migration testing
are as follows:
 Pre-migration testing
 Migration testing
 Post-migration testing
 Roll back testing
Test cases for database migration testing are as follows:
Test case # Test case description
T001 Query executed in the new database yield same results at the of the older one.
T002 Verification of all the queries that needs to be executed in the newer database as
that of the older one.
T003 Verification of all the queries that needs to be executed in the older database using
an automated tool.
T004 Verify that there exists no redundancies within the database and it performs as
expected.
T005 Verify whether any changes that needs to be incorporated in applications updates
have correct values
T006 Verification of table structures, relationships, schema and set back to correspond
to older database.
T007 Verification of newer database connection and whether it has been given the
essential components of the system namely Application, Interfaces, Network
12

connectivity, Server interfaces among others.
T008 Verification of time latency in query execution and whether it is same or faster
than previous one.
The test case is marked “PASS” when it executes the queries as required and generate same
output like that of previous database.
13

References
Cohen, S., Dori, D., & De Haan, U. (2010). A Software System Development Life Cycle
Model for Improved Stakeholders’ Communication and Collaboration.
International Journal Of Computers Communications & Control, 5(1), 20.
http://dx.doi.org/10.15837/ijccc.2010.1.2462
Karim, N., Albuolayan, A., Saba, T., & Rehman, A. (2016). The practice of secure software
development in SDLC: an investigation through existing model and a case study.
Security And Communication Networks, 9(18), 5333-5345.
http://dx.doi.org/10.1002/sec.1700
Kaur, A. (2015). Suitability of Existing Software Development Life Cycle (SDLC) in
Context of Mobile Application Development Life Cycle (MADLC). International
Journal Of Computer Applications, 116(19), 1-6. http://dx.doi.org/10.5120/20441-
2785
Sharma, P., & Singh, D. (2015). Comparative Study of Various SDLC Models on Different
Parameters. International Journal Of Engineering Research, 4(4), 188-191.
http://dx.doi.org/10.17950/ijer/v4s4/405
14