Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Now it is a complete file that have soution of first assignment of SRE
Typology: Assignments
1 / 9
This page cannot be seen from the preview
Don't miss anything!
On special offer
nd
During the current Covid-19 pandemic, you have been assigned a role of Requirement Engineer for the development of an online MIS for a newly developed hospital reserved for coronavirus patients. The MIS will keep the record of all the patients as well as of the complete staff of hospital. Moreover the system will load the data into National Database after every two hours regarding the current situation/condition of patients. Being a requirement engineer, you are required to identify the following in detail
1.1- Add Patients:- The online MIS shall allow front-desk staff to add new patients to the system. 1.2- Assign Patient ID:- The online MIS shall allow front-desk staff to give each patient an ID and add it to the patient’s record. This ID shall be used by the patient throughout his/her stay in the hospital. 1.3- Update Patients:- The administrative staff in the ward shall be allowed to update the personal information of the admitted patient in the hospital. 1.4- Delete Patient ID:- The administrative staff in the ward shall be allowed to delete the ID of the patient from the system when the patient checks out 1.5- Add to Beds-Available List:- The administrative staff in the ward shall be allowed to put the beds just evacuated in the beds-available list.
4.1- Patient Mandatory Information:- Each patient shall have the following mandatory information: first name, last name, phone number, personal health number, address, postal code, and city, country, patient identification number (Id). 4.2- Staff Mandatory Information:- Each staff member shall have the following mandatory information: first name, last name, phone number, designation, working scale, address, postal code, city, country, staff identification number (Id). 4.3- Mandatory Patient Statistics:- In the hospital's statistics section shall have the following mandatory information: Recovered patients, Critical condition patients, and the total deaths in hospital. 4.4- Mandatory Synchronization:- Synchronization of this online MIS database will be made with the National Database Information System after every 2 hours.
1.1- Response Time:- The system shall give responses in 1 second after checking the patient's information. 1.2- Capacity:- The System must support 10000 people at a time. 1.3- User-interface:- The user-interface screen shall respond within 5 seconds. 1.4- Conformity:- The systems must conform to the Microsoft Accessibility
2.1- Patient Identification:- The system requires the patient to identify himself/herself using patient Id 2.2- Logon ID:- Any user who uses the system shall have a Login ID and Password. 2.3- Modification Any modification (insert, delete, and update) for the Database shall be synchronized with the national database of COVID'19 and only by the administrator 2.4- Front Desk staff Rights:- Front Desk staff shall be able to view all information in pandemic online MIS, add new patients to online MIS but shall not be able to modify any information in it. 2.5- Administrators' Rights:- Administrators shall be able to view and modify all information in pandemic online MIS.
How general the form generation language is Simplicity vs. functionality of the form language= Speeds up form development but does not limit functional.
The system shall be available all the time.
Humans are error-prone, but the negative effects of common errors should be limited. E.g., users should realize that a given command will delete data, and be asked to confirm their intent or have the option to undo.
Good quality of the framework= produces robust, bug-free software which contains all requirements Customer satisfaction.
Is part of the code going to be used elsewhere= produces simple and independent code modules that can be reused.
Find the research paper named “RE-Paper 1” attached with this assignment. Read the complete paper multiple times and answer the following questions comprehensively in your own words.
Solution: Traditional Requirements Engineering (RE) approach is the identified problem in this paper.
Solution: The author has solved the identified problem with the help of the agile requirements engineering (RE) approach. As the agile approach is the practice of continuous iteration of development and testing throughout the development life cycle of the project. And the author suggests that if we apply this similar approach in requirements engineering instead of the traditional requirements engineering approach. Then we can improve the requirements change management and its adaptability in a much easier and efficient way. And for this, we should apply proven traditional requirements engineering approaches and agile requirements engineering approach combined. In agile approach requirements, engineering activities are being performed in parallel with product development. So, we must take feedback from the product development team periodically and should develop the requirements accordingly. Because the agile approach provides us with clear specification and validation of requirements and it is among the modern approaches of requirements engineering.
The agile RE has implemented using two tools; one is that the Extended Impact Map for a visible representation of requirements, and the other is that the Kanban board for visualization of progress. Impact Mapping may be a useful gizmo, and therefore the author has discussed this tool's limitations with a proposed solution for every limitation. 1- It mixes two perspectives on Impacts. First is that the customer perspective and therefore the second is that the development company perspective; and to beat this limitation the author separates the map into two, "Customer Impact Map" and "Development Company Impact Map", so that we could focus more on each point of view. 2- It cannot distinguish if a hypothesis was validated or not by just watching the map; and to beat this limitation the author suggests adding some styles to supply rich meanings. 3- Cannot keep track of adjusting progress. A map is simply the static requirement snapshot at a selected time, and to beat this limitation the transition between snapshots must be managed and visualized. The utilization of a Kanban board are often a superb option to track the progress. 4- Cannot readily see how stories flow as a meaningful backbone story for patrons. And to beat this limitation User Story Mapping is a pivot tool that enhances the Impact Map to point out and build the backbone story. Because agile development is customer-centered, in most cases we always use the "Customer Impact Map". At first, we identify customers (or stakeholders) by listing our product usage scenarios. After customer definition, the relative importance of the listed customers is to be analyzed consistent with their level of interest and influence, and therefore the higher the priority, the thicker line between the goal and therefore the customer becomes. During customer analysis, profiles of the customers are created and linked to their needs and pain. The author has considered the cost-effectiveness of delivering value to customers by using the resources of the event company. From the development company's perspective, the target of achieving the customer's goals is an expectation that the customer might contribute to the development company's sub-goals. The author draws a goal tree during a similar way of Customer Impact Map. The sole difference is that the third layer isn't needs, pain, and solutions for a customer but is sub-goal which is predicted to a customer by the event company. At the start of every iteration, the author moves high priority hypotheses (by customer value, risky, then on) from the “Customer Impact Map” to the “Backlog” a column within the Kanban board. To more specialize in customers, the author took swim lanes for every customer on the Kanban board. No matter which agile process follows, when an iteration begins, the Validated Learning process starts. After an iteration ends, counting on the results of the experiment, an item is added, modified, expanded, or deleted within the “Customer Impact Map.” And here we'd like to take care of two Kanban
