Assignment Task (Assignment Number: UA507)
ITAP2013
SOFTWARE ENGINEERING
Assignment-1
July 2021
ITAP2013 SOFTWARE ENGINEERING
Copyright © 2021 VIT, All Rights Reserved.
Individual Assessment:
Weightage: 10%
Report deadline: Week 10.
Objective(s)
This assessment item relates to the unit learning outcomes as in the unit descriptor. This
assessment is designed to improve student skills and to give students experience in constructing
a range of documents as deliverables form different stages of the Software Engineering Process
using a simulated industry case study.
Case Study: Mentcare system
The mid-Scotland health-authority has a statutory duty to provide mental healthcare services to
citizens living in the mid-Scotland area. Most mental health patients do not require dedicated hospital
treatment but need to attend specialist clinics regularly where they can meet a doctor who has
detailed knowledge of their problems. The health authority has a number of day clinics that patients
may attend in different hospitals and in local health centres. Patients need not always attend the same
clinic and some clinics may support ‘drop in’ as well as prearranged appointments. All patients seen
at clinics have been referred to the clinic either by their own doctor, by doctors in Accident and
Emergency when they have attended for treatment or by hospital doctors, when they have completed
a course of hospital treatment. The nature of mental health problems is such that patients are often
disorganised so may miss appointments, deliberately or accidentally lose prescriptions and
medication, forget instructions and make unreasonable demands on medical staff. The Mentcare
system must therefore be able to cope with patient unpredictability and irregular attendance at clinic
sessions. The patient information system to support mental health care (the Mentcare system) is a
medical information system that maintains information about patients suffering from mental health
problems and the treatments that they have received. The Mentcare system has to provide both
management and clinical information:
- Management information that allows health service managers to assess performance against
local and government targets and to monitor the costs of treatment. - Clinical information on medical history, diagnoses and treatments
The system is used to record information about patients (name, address, age, next of kin, etc.),
consultations (date, doctor seen, subjective impressions of the patient, etc.), conditions and
treatments. Reports are generated at regular intervals for medical staff and health authority
managers. Typically, reports for medical staff focus on information about individual patients
whereas management reports are anonymized and are concerned with conditions, costs of
treatment, etc
ITAP2013 SOFTWARE ENGINEERING
Copyright © 2021 VIT, All Rights Reserved.
What to Submit
Please read the above case study carefully, and then answer the following questions based on the
case study.
Question 1
Given the Case Study above, what SDLC Model would you use to develop the associated software. You
will need to justify your answer. Outline the advantages and disadvantages your SDLC model would
have over other SDLC models that could be utilized in developing the software.
Question 2
Creare a software requirement specification which includes the following
I. Identify four types of System users. (system user: that may make use of the Mentcare system).
II. A detailed decription of both user and system requirements. (At least four user requirements
and four system requirements should be provided).
III. A detailed decription of both functional requirements and non- functional requirements. (At
least four functional requirements and four non-functional requirementsshould be provided).
INSTRUCTIONS:
The above list of documents is not necessarily in any order. The chronological order we cover
these topics in lectures is not meant to dictate the order in which you collate these into one
coherent document for your assignment.
Your report must include a Title Page with the title of the Assignment and the name and ID. A
contents page showing page numbers and titles of all major sections of the report.
All Figures included must have captions and Figure numbers and be referenced within the
document. Captions for figures placed below the figure, captions for tables placed above the
table. Include a footer with the page number. Your report should use 1.5 spacing with a 12 point
Times New Roman font. Include references where appropriate. Citation of sources is mandatory
and must be in the IEEE Style.
All submissions are to be submitted through turn-it-in. Drop-boxes linked to turn-it-in
will be set up in the Unit of Study Moodle account. Assignments not submitted through
these drop-boxes will not be considered.
Submissions must be made by the due date and time (which will be in the session detailed
above) and determined by your Lecturer. Submissions made after the due date and time
will be penalized at the rate of 10% per day (including weekend days).
ITAP2013 SOFTWARE ENGINEERING
Copyright © 2021 VIT, All Rights Reserved.
The turn-it-in similarity score will be used in determining the level if any of plagiarism.
Turn-it-in will check conference web-sites, Journal articles, the Web and your own class
member submissions for plagiarism. You can see your turn-it-in similarity score when
you submit your assignment to the appropriate drop-box. If this is a concern you will have
a chance to change your assignment and re-submit. However, re-submission is only
allowed prior to the submission due date and time. After the due date and time have
elapsed you cannot make resubmissions and you will have to live with the similarity score
as there will be no chance for changing. Thus, plan early and submit early to take
advantage of this feature. You can make multiple submissions, but please remember we
only see the last submission, and the date and time you submitted will be taken from
that submission. Below is the plagiarism penalty criteria.
Please Note: All work is due by the due date and time. Late submissions will be penalized
at the rate of 10% per day including weekends.
Assignment Solution/Sample Answer
Software Development life cycle
Hospital Management System Types 5
User and System Requirements Concept 6
Requirements for Functionality: 8
SRS Registration Procedure (Software Requirements Specification) 9
Non-functional Prerequisites 9
Question 1
The V-Model
This concept places a strong focus on the process’s continuous course of execution. That is, each step must be completed before moving on to the next. This paradigm is identical to the waterfall model, with the exception that this model places a greater emphasis on testing than the waterfall approach. Thetesting methods Before the scripts are produced, the programme is developed.each of the stages before software configuration.
The V-shape approach, like the waterfall model, begins with a needs analysis. The first stage prior to the design phase is to establish a test strategy for the system, with a strong emphasis on satisfying the functionality provided in the analysis stage. At the architectural and design stages, as well as the integrating test plan, everything is built and developed.Phase of elevated design This step is critical since the software must be tested to see whether the parts produced thus far can operate together like a unit. However,the computer structures are created solely during in the low-level design phase, with test automation necessary to test the features of the application.The programme is coded during the project execution, and once completed, the remaining developing phase proceeds on the right side of the screen of V, where the previously prepared testing plans are now implemented.make advantage of Figure 3 depicts the V-shape gives a framework.It should be mentioned that the V-shaped form has its own set of benefits and drawbacks.They are detailed below.
It must also be mentioned that the V-shaped model has its own set of benefits and drawbacks, which are outlined below (Chiasson, 2018).
Advantages
- Extremely simple and straightforward to use
- Each stage has its own set of objectives.
- It has a better probability of success since it develops test plans earlier in the life cycle, something the waterfall approach does not have.
- This is an excellent approach for small jobs with straightforward needs.
Disadvantages
- A significant drawback of this strategy is that the software is developed during the implementation phase without the need for a prototype.
- It follows a strict method, similar to the waterfall model.
- Because this approach is rigid, making modifications can be difficult and costly.
- If an issue is discovered even during model’s development process, there is no obvious path offered during the testing stage.
Question 2
PART 1.
Hospital Management System Types
Simply defined, hospital software suite software is any software that streamlines normal management operations and saves all information needed to administer a medical facility.A hospital system software should be designed if you wish to unify and offer quick access to information regarding employees, patients, suppliers, billing, and statistics. Furthermore, the management system may include integrated telemedicine options.
Essentially, with such a management solution, a hospital’s staff have a multi-purpose digital tool that assists them in doing daily duties with minimum effort.Health centre management platform varies in complexity, scale, and usefulness based on the needs, size, and budget of a medical facility. Despite the fact that the capability of hospital software varies greatly from one business to the next, the four main categories of clinic management systems may be described (Chiasson, 2018).
- Tactical level intelligence classifications and strategic online
- Hospital administrative systems for handling admin interactions with patients
- Subject-specific systems, including such Electronic Patient Records (EMRs) or Electronic Health Records (EHRs) (EHRs)
- Task-based systems, such as hospitalisation systems, are connected with particular tasks.
- Billing solutions for financial monitoring and management.
Of addition, the health information system might incorporate many types of software or functionalities. There are no hard and fast rules for developing hospital software. A digital solution for a clinic may be created to be a great fit for the specifications and objectives of a certain firm.
School Management System Types
School management system will assist in managing everyday school activities including student enrolment, subject assignment teachers with subject matter, teacher management, student degrees, student examination and leave management system.
For complete school management ERP, we have design demo database.
Full PDF can be downloaded
- Class Rooms
- Grades
- Course
- Students
- Parent
- Student Classroom
- Attendance
- Exam
- Exam Type
- Exam Result
- Teacher
- Teacher Department
- Teacher Type
Traffic Management System Types
Here are typical cases of use that must be addressed in order to manage traffic effectively:
The number of vehicles entering and leaving a specific area or within a certain area of interest may be counted by the traffic management application.
They must also be able to identify and count the class of vehicles that pass from the field of view of the camera (e.g. truck, car and Scooter).
Features:
Function extraction methods are used to solve common problems such as object detection and reconnaissance in computer views.
Oriented gradient histogram (HOG) is one of the extraction methods used to detect objects.
HOG is used for feature extraction on a labelled training set of images in the current vehicle classification and counting application.
A HOG relies on the property of objects within an image to process intensity gradients or border directions distribution.
In an image per block, gradients are calculated.
A block is a pixel grid in which the gradients of the intensities of the pixel in the block are composed of the magnitude and direction of change.
Bank Management System Types
This database was produced on the basis of banking requirements.
The system is able to encode customer data.
Banking administrator can have customer status access and important transaction information.
You may handle the necessary data for the management of customer, employee, and customer and staff transactions.
Security and monitoring of customer records, transactions and status were the features included in the ER system diagram.
These characteristics have also been listed and registered in reports which have served as the transaction history in the system.
- Functions Description of bank management system
- Database tables of the bank management system
- Bank Management System Schematic Diagram
- Bank Management System ER Diagram
Telecommunication Management System Types
Telecommunications are not easy to handle.
This category of expenditure frequently includes old equipment, acquisitions, technological changes and complex contracts.
Each item’s visibility is essential to managing and tracking your inventory effectively.
This is particularly true when you plan to change providers and need transparency and reporting in order to get competitors to provide precise price proposals.
You need accurate telecom service, device and feature tracking to provide more visibility in telecommunications expenditure.
Seek a reliable supplier that can deeply immerse your telecommunications infrastructure.
A robust inventory system for telecommunications can produce reports from MPLS nodes to phone logs.
Reduce the time and effort needed to keep the wireless inventory detailed.
In general, the following tasks are included:
Arrange your wireless inventory information
Enter all plans, equipment, circuits and lines
Enter all telecom orders and requests for changes
Please include sites, GL codes and users
Part 2.
Health Management User and System Requirements Concept
The technical specifications are the specifications of the services that a system should offer as well as the limitations on its functioning. Customers’ demands for a system that performs a certain function, such as operating a gadget, placing an order, or obtaining information, are reflected in these criteria. The process of discovering, evaluating, documenting, and testing these services and restrictions is referred to as requirements architecture.
Some of the issues that emerge throughout the requirements specification process are caused by a failure to clearly separate these distinct levels of specification.
- User objectives are identified in human language with diagrams that describe the services that the system is expected to deliver to system users as well as the restrictions that it must function under. User requirements might range from broad assertions of needed system features to comprehensive, exact specifications of system functioning.
- Technical specifications are more thorough definitions of the functions, services, and operational restrictions of a software system. The system requirements document (also known as a functional specification) should specify precisely what will be implemented. It might be spelled down in the agreement between the system purchaser and the software engineers (Bersoff, 2020).
This case study from the mental care patient records system demonstrates how a user demand may be extended into numerous requirement specification. Figure shows that the user need is fairly broad. The technical specifications detail the services and functionalities of the system that will be delivered.
B ecause various types of readers utilise requirements for different ways, you must express them at varying degrees of depth. The diagram below depicts the many types of readers for the user and the technical specifications.
Readers of user needs are not mainly worried with how the system will be implemented, and they may be executives who are just not concerned in the system’s specific capabilities. Readers of requirements need to know more exactly what the platform will accomplish since they are concerned about how it will assist business operations or are engaged in systems development (Bersoff, 2020).
The manticore system consists of the following components:
- Individuals who data is stored in the system, as well as their family
- Physicians who are in charge of evaluating and treating patients.
- Nurses who organise doctor-patient consultations and perform some treatments.
- Medical reception staff are in charge of appointment scheduling for patients.
- IT personnel who are in charge of implementing and maintenance of infrastructure.
- A regarding medical manager must ensure that the system adheres to current ethical norms for patient treatment.
- Managers of health care facilities who get managerial data from the system (Chiasson, 2018).
Bank Management User and System Requirements Concept
A project based on relevant technology, BANK MANAGE MENT SYSTEM is implemented.
The principal objective of this project is to develop banking system software.
This project is designed to develop banking system software.
This project was developed to easily and quickly carry out the processes that cannot be carried out with the manual systems overcome by the software.
This project is created with the language and VB.
The solution for the current management system is therefore comprehensive.
Ambiguity, incompleteness and inconsistency are prone to requirements.
Techniques such as rigorous inspection have been demonstrated to help address these problems.
Ambiguities, incompleteness and inconsistencies, which are usually less costly than to correct in subsequently stages of product development at the requirement phase, are resolved (Chiasson, 2018).
Analysis of requirements seeks to deal with these problems.
- Take a long time to produce
- Begin to limit the implementation option available
- Are costly to produce
Traffic Management User and System Requirements Concept
Ambiguity, incompleteness and inconsistency are prone to requirements.
Techniques such as rigorous inspection have been demonstrated to help address these problems.
Ambiguities, incompleteness and inconsistencies, which are usually less costly than to correct in subsequently stages of product development at the requirement phase, are resolved.
Analysis of requirements seeks to deal with these problems. Take a long time to make it.
Start to restrict the available implementation option.
In general, existing monitoring systems collect information on traffic flow that includes mainly traffic parameters and detection of traffic incidents.
Detection of traffic incidents is more difficult and has great potential for research.
While great progress has been made in video monitoring, researchers continue to face different challenges and difficulties in practical ITS applications.
The current challenges for video-based monitoring systems are summarised as follows:
- For night time operation, additional lighting equipment can be used, but the visual range is usually limited.
- Occlusion of vehicles: In busy traffic scenarios other vehicles or no vehicles such as football, biking and trees and buildings can easily occlude vehicles.
- Pose change: when turning or changing lanes, the position of the vehicle can vary considerably.
- Various types of vehicles: different shapes, dimensions and colours, there are different vehicles.
Telecommunication Management User and System Requirements Concept
- Layer of Element Management, this layer addresses the management of network element functions. Examples of these features are equipment errors detection, environmental conditions such as energy and temperature consumption, resource measurement such as the use of CPU, disc and message queue and software upgrades.
- Layer for Network Management
This layer focuses on the network elements’ interaction and network
topology. Examples of the role of this layer are network topology configurations,
routing and signalling paths establishments and the aggregation of network failure and
measurement conditions.
- Layer of Service Management
This layer covers the aspects of the network that the users of the network can
experience. The quality of service (QoS)/quality of experience (QoE), accounting,
user management, and so forth are examples of these network aspects.
Part 3.
Requirements for Functionality:
There are several software needs specifications contained in the acceptance criteria of the Hospital Management System, which includes several processes, including Registration, Checkout out, Reporting Generation, and Database.
SRS Registration Procedure (Software Requirements Specification)
Adding Visitors: The Healthcare Management allows front-desk personnel to add new service users to the program.Assign specific an ID to the visitors: The HMS allows the front-desk personnel to offer an interesting ID for each patient, which is subsequently added to the participant’s record book. The ID can be used by the patients during their hospital stay.
SRS Check Out:
Erase Patient ID: Whenever a patient checks out of the facility, the personnel in the administrative area of the hospital may remove the client ID from the system.
Add it to the list of rooms available: Staff in the administrative part of the ward can place an empty bed just on list of bed capacity (Chiasson, 2018).
SRS Report Generation:
Client Info: The Hospital Management System creates a report on each patient that contains information such as the patient’s name, mobile number, bed multitude, the doctor’s designation to whom it is assigned, ward name, and much more.
Availability of the Bed: The Management System also assists in the reporting on the accessibility of the bed, including data such as bed number empty or filled, ward names, and more.
SRS database:
Required Client Details: Every patient must provide certain information such as their mobile number, very last name, individual health amount, postal code, country, location, city, ‘child’s Identification number, and so on.
Changing Patient Data: The management software allows users to change the patient health information as stated in the mandatory information contained (Bersoff, 2020).
Non-functional Prerequisites
There are many software needs specifications contained in the Patient Care System’s quasi demands, which cover different processes such as security, efficiency, ease of maintenance, and durability.
Confidentiality:
- User Recognition: The technique requires the patient to use the phone to identify himself or herself.
- Logon ID: All users who interact with the system must have a Logon ID and password.
- Adjustments: Any database changes such as insert, remove, update, and so on may be synced rapidly and done exclusively by the ward administrator.
- Front Desk Employees Rights: Back desk staff have the ability to read any data in the Health Board System and add new patient records to the HMS, but they do not have the capacity to modify any information in it.
- Administrator privileges: The administration has the ability to access and modify any material in the Hospital.
Effectiveness:
- Refresh Rate: Once the ‘participant’s credentials is verified, the system delivers confirmation in less than one second.
- Capacity: The system is required to accommodate at least 1000 users at the same time.
- Consumer: Within 5 seconds, the interface recognizes.
- Subservience: The software must guarantee that the Windows accessibility requirements are met.
Consistency:
- Back-up: The technology provides efficient data backup.
- Errors: The program will track all errors and keep a log of the
Serviceability:
- Access: The system is always available.
- I hope you’re enjoying understanding of system and non-functional requirements, as well as the required features by hospital. Any more questions about the subject are welcomed.
Conclusion
Software Development life cycle that is designed to computerise the day-to-day operations of a local clinic and is able to store material such as patient registration, health records, and physician data in a simple and efficient manner. The system may also provide test results, pharmaceutical prescription data, and nutrition suggestions. An acute or outpatient invoicing facility is available. This technology’s feature, and most significantly, a backup facility, is incorporated in the software. In the case of an unforeseen crash. Given the complex nature of the software development lifecycle and life cycle was difficult and hard, thus this project required a significant amount of manpower, code, and research to be accomplished. The main goal of this project is to create a comprehensive package of healthcare information software for Spectrum Specialized Medical Clinic, which is why development took so long, but what is displayed in this thesis is restricted to a few components due to an agreement between it and the firm.
REFERENCES
- Assal, H., & Chiasson, S. (2018). Security in the software development lifecycle. In Fourteenth Symposium on Usable Privacy and Security ({SOUPS} 2018) (pp. 281-296).
- Bassil, Y. (2019). A simulation model for the waterfall software development life cycle. arXiv preprint arXiv:1205.6904.
- Davis, A. M., Bersoff, E. H., & Comer, E. R. (2020). A strategy for comparing alternative software development life cycle models. IEEE Transactions on software Engineering, 14(10), 1453-1461.
- Leau, Y. B., Loo, W. K., Tham, W. Y., & Tan, S. F. (2019). Software development life cycle AGILE vs traditional approaches. In International Conference on Information and Network Technology (Vol. 37, No. 1, pp. 162-167).
- Nurmuliani, N., Zowghi, D., & Powell, S. (2018, April). Analysis of requirements volatility during software development life cycle. In 2004 Australian Software Engineering Conference. Proceedings. (pp. 28-37). IEEE.
- Ragunath, P. K., Velmourougan, S., Davachelvan, P., Kayalvizhi, S., &Ravimohan, R. (2019). Evolving a new model (SDLC Model-2010) for software development life cycle (SDLC). International Journal of Computer Science and Network Security, 10(1), 112-119.
- Ruparelia, N. B. (2019). Software development lifecycle models. ACM SIGSOFT Software Engineering Notes, 35(3), 8-13.
Download the sample solution for the above mentioned assignment or order an fresh assignment. Universal Assignment is always ready to do it for you.
