Hashara_EWSD.pdf

8 Different User Groups Login Credentials .... 21 List of Tables Table 1: Different User Groups Login Credentials .... Here, the 2 user groups have different privileges when dealing t

Enterprise Web Software Development

(Individual Report)

Course : COMP1640 Enterprise Web Software Development

Report Types : Individual Documentation

Submitted by : Hashara EDIRIWEERA

UoG Reg No : 001028024

Dated : 12th April 2018

Tasks : 1, 2, 3, 4

Table of Content

Acknowledgement 2

Table of Content 3

List of Figures 5

List of Tables 5

Introduction of the University of Hartvak 6

Introduction to the Project 6

URL of Hosted Website 8

URL of Screencast 8

Group Common Email Login Credentials 8

Different User Groups Login Credentials 8

Evaluation for the Productive Outcome 9

Use of the Project 10

Similar Sites Research 11

Description of Similar Sites 13

Evidences 13

Project Evidence 13

Product Evidence 13

Agile Methodology Usage Evidence (Phases not completed 1 after the other) 13

Team and Self Evaluation 14

Team Weight Achievement 14

Team Contribution throughout the Project 15

Self-Evaluation throughout the Project 17

Critical Review 18

SWOT Analysis 18

Lesson Learnt Report (Individually) 19

Future Enhancement 20

Conclusion 20

APPENDIX A – Group Common Repository Drive with Login Credentials 21

Hosted Wed URL 21

Database SQL Commands 21

Project’s Group Documentation 21

Wireframes 21

Entity Relationship Diagram 22

Data Dictionary of the entire system 22

Meeting of Minutes 22

Sprints 22

Screenshots of System Interfaces 22

Entire Testing 22

UML Diagrams (Class, Use Case, Sequence, Activity Diagrams) 22

Other Diagrams 22

Screencast of the Presentation 23

Product Backlog 23

APPENDIX B – Team member names and their roles 23

APPENDIX C – Document’s Abbreviations 24

APPENDIX D - References 24

List of Figures

Figure 1: a) Similar Site to UoH Site 11

Figure 2: b) Similar Site to UoH Site 11

Figure 3: c) Similar Site to UoH Site 12

Figure 4: Username & Password of the repository email in Appendix - A 21

List of Tables Table 1: Different User Groups Login Credentials 8

Table 2: Evaluation for the Productive Outcome 9

Table 3: Team Weight Achievement 14

Table 4: SWOT Analysis 18

Table 5: Lesson Learnt Report (Individually) 19

Table 6: Team member names and their roles 23

Introduction of the University of Hartvak

The University of Hartvak (UoH) is large university in London This university was established in the year of 1977 The UoH provides the best educations and the most standard educational degrees for students Since, it is a large educational sector in London, it has mainly 5 different streamed faculties They are IT, English, Biology, Engineering and Architecture faculties The population of the UoH is approximately 11,000 of students including both undergraduate and postgraduate students Recently the UoH required a web-enabled role-based system in order to increase the university productivity and for the improvement

Introduction to the Project

Nowadays, the technology has immensely been increased With the involvement of technology, the manual procedures are being automated and functions as computerized systems The majority of the universities and companies uses fully automated systems This leads to make the work effective and efficient When considering the present universities, almost all the universities has their own systems to proceed with whatever their procedures For example, students’ registrations, lecturers’ salary generations, lecture hours scheduling, students’ attendance, students’ evaluation results generation and etc all of these processes are being automated throughout an entire system

The University of Hartvak requires a secure web-enabled role-based system which can also be accessed by a mobile device, in order to increase the productivity and for the improvements of the university This idea is much advantageous and beneficial because all students and staff members can get registered to the site and produce their own ideas

or comments Moreover, since this is not a much complex task to do everybody can register and proceed accordingly

When describing about the requirements specification, there are number of requirements to be included while the system is in development stage The main objective is to provide the ability for the students and staff to provide their ideas in the site Those use groups can also provide their opinions by a thumb-up or a thump-down for the commented comments Here, the 2 user groups have different privileges when dealing though the site, where students cannot view staff comments and only staff can view students and staff both user groups’ comments Moreover, there are 3 more user group levels such as a quality assurance manager, the quality assurance coordinators and an administrator Here, the quality assurance manager can control and oversee the entire running of the system and all the departments And, the QA coordinators are being assigned to control and to oversee only their relevant departments Lastly, the administrator can proceed with all the modifications and all the functions with the entire system

Covering all these requirements the website URL and the screencast will show, how the system will be functioned And all the other tasks included in the group report are linked below and in order to access all the tasks in the email drive, the email credentials are given below

URL of Hosted Website

http://www.jasontest.byethost32.com/Group%20Project%20Web%20Site/project/

URL of Screencast

https://drive.google.com/file/d/1cDfRDrB8jYTh8wz3b1cnskFh3dGTpZ1n/view?usp=sharing

Group Common Email Login Credentials

Username : uogbit2018@gmail.com

Password : uog@2018VHJT

All the tasks including the diagrams in the group report are stored in the above email drive Below, in the appendix – A, all those diagrams are linked

Different User Groups Login Credentials

Table 1: Different User Groups Login Credentials

User Groups User Credentials

User Name Password

Administrator hasharaadmin@gmail.com max04.admin

Evaluation for the Productive Outcome

Table 2: Evaluation for the Productive Outcome

1

Objective: Similar university sites researches

Task: Make researches on similar sites via internet in order to get clear

idea on how the new system looks like

Deliverables: Get a better idea on what the system is based on, how the

system should look like and what the system should include

2

Objective: Analyzing the requirements for the new university system

Task: Collecting the right requirements by conducting requirement

gathering techniques

Deliverable: Get a better knowledge on what exactly the client requires

3

Objective: New system designing

Task: Designing the new system structure using UML diagrams, ER

diagrams, wireframes and so on

Deliverable: Makes it easy in developing the system

4

Objective: New system development

Task: Coding the program using an editor to bring the system into real

word

Deliverable: To produce a system which functions according to the

gather reequipments

5

Objective: New system testing

Task: Creating a test schedule and test cases

Deliverable: Test results and to get an error free system

6

Objective: New system implementation

Task: Finding the right hardware and software to run the new system

Deliverable: To make sure the system operates within the

implementation location

7

Objective: New system maintenance

Task: Creating a user manual for the new system

Deliverable: To carry out the duties within the system in a correct

manner

Use of the Project

Since, the world has immensely evolved, the technology has also parallelly increased The majority of the people are so much on to the technology, where they interact with new inventions and new innovations Most of the business organizations such as software firms, hospitals, banks, universities and etc the most of these firms consists

of automated systems where they eliminate the manual procedures Using automated systems, it makes the work load to be carried out much effectively and efficiently When considering the newly implemented web-enabled roles-based system of the University of Hartvak, it is much more important and considerable, because it eliminates the manual procedures and functions many functionalities from that system, instead of having many categorized manual procedures Since the new system can cover

an extensive number of requirements, it is also much easier for the users to handle many situations from that single system itself For example, providing comments, registration, liking, communications and so on In addition to that, the site is a well secured system where only the relevant person can see his or her personal information Therefore, on the other hand this system provides a well secured access as well

So mainly, this system is implemented in order to increase the productivity and the improvement of the university including the above-mentioned points as well

Figure 1: a) Similar Site to UoH Site

Figure 2: b) Similar Site to UoH Site

Similar Sites Research

(education, 2018)

(STV Anglistik und Amerikanistik, 2018)

Figure 3: c) Similar Site to UoH Site

(Uni Reviews, 2018)

Description of Similar Sites

The above shows some figures of similar university websites of University of Hartvak

In the above figures the main issue is that they cannot like or dislike any comments commented Where, our implemented system consists that functionality in order to get the users likes for a certain comment Moreover, when considering the website of the University of Deakin, it is not that much user friendly and lack the attraction towards the user Therefore, it is a necessity that the interfaces should be much colorful and pleasant to deal with

Evidences

Project Evidence

http://www.jasontest.byethost32.com/Group%20Project%20Web%20Site/project/

Product Evidence

See URL of Hosted Website

See URL of Screencast

Agile Methodology Usage Evidence (Phases not completed 1 after the

other)

https://drive.google.com/file/d/1zkwWZtJGAyNBeE6BAgGloY0DDpnN1HEP/view?usp=sharing

https://drive.google.com/file/d/1_egQgzWaRwSotkI2SVCIWeG0jaBHROt7/view?usp=sharing

Team and Self Evaluation

Team Weight Achievement

Table 3: Team Weight Achievement

Date: 14/03/2018 Performance Color Grades:

Excellent - (101 - 120)

⚫ Good – (81 - 100) ⚫ Neutral – (61 - 80) ⚫ Weak - (41 - 60) ⚫ Very Weak - (1 - 40) ⚫

Tasks

ID Tasks

Team Members’ Names

Hashara Jason Viyasika Tharuka Fathima

The above table shows the team performance and how they contributed to the project

I have calculated each person’s tasks by maximum 10 points And since there are 12 tasks, I have multiplied the number of tasks (12) by 10 And, rated for 120% in overall

Team Contribution throughout the Project

The team has decided to divided the work load, majorly into 5 sprints and allocate the team members in the 5 sprints Moreover, we have allocated 5 scrum meeting for each sprint of the project This makes easy for the team members in carrying out the meeting

on the relevant sprint only Below shows a detailed summary on how the team members contributed individually in my point of view

In the 1 st sprint there were 6 tasks to be completed in 13 days They are, making

researches on similar websites, analyzing the right requirements, sketching the rich picture, getting the requirements specification and then prioritize all the requirements according to MoSCoW prioritization and drawing wireframes of certain interfaces In consideration of researching similar sites, all the team members were engaged on that task and did different researches on similar sites Here, all the team members were able

to get the most similar sites and to get a clear idea on how the system should look like and its content Since, I am the requirement analyzer I had to get the right requirement Therefore, I was able to get all the right requirements on time and to provide them to Tharuka who was the information architect He did a good job in prioritizing the requirements according to MoSCoW prioritization Since, we had a limited time duration, Tharuka was able to provide the prioritized requirement on time to the system developer Rich picture and wireframes were drawn by Viyasika who the front-end web designer was She also did a great job in analyzing the similar site and get a clear idea

on how the wireframes should be drawn by herself She contributed greatly in all the other sprints where she had to draw wireframes Same with the rich picture drawn by Viyasika

In the 2 nd sprint it is all about designing the system’s structure There are 5 tasks to be

completed from 12 days Drawing UML diagrams, Database designing / developing, ERD, drawing wireframes, web designing and testing were the tasks Here, the UML diagrams were drawn by Viyasika and Tharuka where other members also gave them a

support They designed it on time so that here also it is easy to start the development The use case diagram was given lately since there were many areas to be clarified But, this wasn’t a big issue since the use case diagram was handed over before the 2nd sprint ends The database side was totally handled by Tharuka where everything was done perfectly He drew the ERD and he decided how the system database should look like and what it should consist In certain areas Tharuka was unable to contact via online to check his updates But it wasn’t an issue since he completed his task before the 2nd

sprint ends Jason was another good team player where he was responsible in designing the website He was mainly stressed with his office matters but amidst those, he was able to complete the design of web on time and gather the team to illustrate his updates Fathima also provide the fullest support in testing responsive in that relevant sprint

In sprints 3 and 4, the tasks are same but the contents of the tasks changes Both have

the development of CMS and a testing part Here, the mainly included team members are Jason and Fathima Once, Jason completed the development, Fathima was able to test the developed sessions accordingly Therefore, in the 3rd and 4th sprints, the tasks were run in a smooth manner covering 9 days in each sprint, altogether 18 days

The last sprint is the 5 th sprint In this task, there were 3 tasks to be completed within

12 days of time duration They are, implementation, user acceptance testing and the entire documentation In this sprint the implementation was done by Jason He sorted out the necessary software, hardware specifications and decided how to implement it

He selected the most effective and efficient specifications for the implementation Moreover, Fathima carried out the user acceptance testing and she was also assigned for that role because she acted as the product owner, where the product owner does the user acceptance testing by the client’s party The documentation was completely done

by me and Viyasika we had many discussions on how to proceed with the documentation Here, we did the documentation in a systematic manner where each and every point is clear for the reader to understand

In overall, all the team members did a great job in completing this project on time There were no critical issues on members when dealing with them throughout the project, since all the team members had a better understanding and the gravity of this project