Nghiên cứu này có thể mở rộng theo hướng tìm cách những quy luật tường minh giúp người dùng lựa chọn sự kiện/trạng thái từ yêu cầu bằng ngôn ngữ tự nhiên, thay vì những nguyên tắc đặt ra dựa vào kinh nghiệm như hiện nay.
Một hướng nghiên cứu khác là đánh giá tính đủ của bộ luật đã xây dựng. Trong luận văn này cũng như các nghiên cứu [2], [4], [6] đều xây dựng và mở rộng các luật dựa trên bộ mẫu kiểm nghiệm mà chưa đề cập đến vấn đề tính đủ của bộ luật. Vấn đề này có thể sẽ được giải quyết nếu dựa trên các lý thuyết về logic và máy hữu hạn trạng thái.
53
Việc kết hợp SPSG và SPSKC (mở rộng thêm cả luật của nhóm nghiên cứu của BOSCH) hiện đang gặp một vấn đề về mặt kỹ thuật là không thể dịch sang cùng một logic (SPSG có thể dịch sang PCTL, PCTL* và CSL trong khi SPSKC có thể dịch sang LTL, CTL, GIL, MTL, TCTL, RTGIL) [2]. Do đó, nghiên cứu này có thể tiếp tục với một hướng đi tham vọng là tìm một ngôn ngữ logic có thể thể hiện chung cho các luật của SPSC. Tuy nhiên, hướng đi này cần nỗ lực tương đối lớn để có thể đưa ra kết quả.
54
TÀI LIỆU THAM KHẢO
1. Allen P. Nikora, Galen Balcom. Automated Identification of LTL Patterns in Natural Language Requirements. 2009. DOI: 10.1109/ISSRE.2009.15.
2. Amalinda Post, Igor Menzel, Jochen Hoenicke. Automotive behavioral requirements expressed in a specification: a case study at BOSCH.
London : Springer, 2012. DOI 10.1007/s00766-011-0145-9.
3. Charette, Robert N. Why Software Fails. IEEE Spectrum inside
technology. [Online] September 2005.
http://spectrum.ieee.org/computing/software/why-software-fails.
4. Cobleigh, Rachel L. PROPEL: An approach supporting user guidance in developing precise and understandable property specifications. 2008. PhD dissertation.
5. Cristina Palomares, Carme Quer, Xavier Franch, Cindy Guerlain, Samuel Renault. A Catalogue of Non-technical Requirement Patterns.
Chicago, USA : IEEE, 2012. REPA. DOI: 978-1-4673-4376-3/12.
6. Grunske Lars. Specification Patterns for Probabilistic Quality Properties. Leipzig, Germany : ICSE, 2008. 978-1-60558-079-1/08/05. 7. Hamid Alavi, George Avrunin, James Corbett, Laura Dillon, Matt
Dwyer, Corina Pasareanu. Specification Pattern System: FAQ's. Spec Patterns.[Online]. http://patterns.projects.cis.ksu.edu
8. IBM Rational Software Documentation. IBM. http://www.uet.vnu.edu.vn/~
hanhdd/ooad2013ss/slide_03b_requirementsEx.pdf
9. Karl E. Wiegers. Software Requirements. 2nd. Redmond, Washington 98052-6399 : Microsoft Press, 2003. ISBN: 9780735623989.
10. Matthew B. Dwyer, George S. Avrunin, James C. Corbett.
Patterns in Property Specifications for Finite-State Verification.
ICSE „99 Los Angclcs CA.
11. Stephen Withall. Software Requirement Patterns. Washington 98052- 6399 : Microsoft Press, 2007.
55
12. Sascha Konrad, Betty H.C. Cheng. Real-time Specification Patterns. St. Louis, Missouri, USA : ICSE, 2005. 1-58113-963-2/05/0005.
13. T, Kuhn. Acerules: Executing rules in controlled natural language.
Berlin : Springer, 2007. International conference on web reasoning and rule.
56
Phụ lục 1: Mẫu yêu cầu “Living Entity Requirement Pattern”
1, Basic Details
Related patterns: Data type, data structure, configuration Anticipated frequency: Up to 5% of requirements
Pattern classifications: Affects database: Yes 2, Applicability
Use the living entity requirement pattern to define a type of entity for which
information is stored and which hass a lifespan (that is, is created, can be modified any number of times, and eventually terminated).
Do not use the living entity requirement pattern for any entity that is part of the system's configuration; use the configuration requirement pattern instead. 3, Discussion
A requirement for a living entity is primarily to define the information that needs to be stored for it (field by field), as well as related details such as how each entity can be uniquely identified (using IDs or other keys). Secondarily, a requirement for a living entity can also cover functions for editing (adding, modifying, and removing) and viewing an entity; these can be achieved either explicitly, or implicitly by the use of pervasive requirements that mandate such functions for all living entities. However, if there's anything particular to be said about any one of these functions, write a separate requirement for that function.
4, Content
A requirement for a living entity must define at least:
1. Entity name Make it clear, unique, and concise.
2. An explanation of the entity This is to make it clear what it is, what it's for,
(and, if appropriate, also what it's not for).
3. The information the entity contains Present this in the form of a data
structure. Usually the requirement itself defines the data structure, but it can alternatively refer to another requirement that defines it. In both cases, the data structure is as described in the data structure requirement pattern. These map roughly to the columns of a database table.
The definition of each item of information can also contain relevant details about the entry, validation, display of its value (including whether it is to be displayed at all), and/or such things as whether it can be amended after the entity has been added. Such information can be included in a requirement defining the data type in question if it applies to all occurrences of it (as per the
57
data type requirement pattern in Chapter 6, "Information Requirement Patterns").
4. The way(s) in which an entity is uniquely identified State its ID (or IDs) plus
any other ways of uniquely identifying it. (These later turn into indexes of a database table.)
5. Parent entity details (If any.) An entity of one type can sometimes only be
created if some other entity already exists. A banking system might insist that a bank account can only be created if the customer it belongs to already exists. Describe the relationship with the parent or parents (because there could be more than one, and they could be different types of entity), including whether it is essential or optional. 5, Template(s) Open table as spreadsheet Summary Definition
«Entity name» The system shall store the following information about a
«Entity name»:
«Data item 1 description».
…
A «Entity name» is «Entity explanation». Each «Entity name»
is uniquely identified by «Entity identifier(s)». [«Parent entity
details».]
6, Example(s) Open table as
spreadsheet Summary
Definition
Basic customer details The system shall store the following information about a customer:
Customer ID (as defined in requirement XR99.1).
Password.
Personal contact details (as defined in requirement
XR99.2).
Credit card details (as defined in requirement
XR99.3).
Date of birth.
Registration date.
Status (active, blocked, or terminated). This is never
displayed to the customer.
58
7, Extra Requirements
See also the "Extra Requirements" section in the introduction to this chapter.
There are several kinds of pervasive requirements that can be written to apply to all living entities, to avoid having to specify them repeatedly for each type of entity. These are:
1. Editing functions We need to be able to add, modify, and remove an entity.
Each function to modify an entity needs to identify which information can be modified (or, if it's more convenient, which cannot). If your system allows people to modify information about themselves, distinguish what they are allowed to change from what other users are allowed to change. For example, a Web shop customer might be able to change their personal details and
preferences; an employee of the shop might be unable to change these things. Refer to the user authorization requirement patterns in Chapter 11 for how to specify in more detail who is allowed to do what.
2. Inquiry functions Specify one to list all the living entities of a certain type (or,
if there are too many to list, some sort of selection or search mechanism), and one to display the details of a selected entity.
3. Change history This is typically a record of every modification to an entity
(including adding and removing). It could either record every changed value (so as to have a complete picture of every change) or merely the fact that something
changed. Knowing every changed value is attractive-but it's also a lot more development effort (and raises other matters-such as restricting access to
sensitive information in change histories), so ask for it only for those entities for which it's justified. If in doubt, leave it out.
4. Common data These are items of information to be present in every type of
living entity. They are typically used for information such as who last changed
an entity and when.
If an adequate change history is maintained for each entity, common data
identifying who made changes and when is not strictly necessary, because it can be derived from the change history.
5. Logical remove only When we ask for a living entity to be removed, we don't
want all trace of it to disappear (because that might cause difficulties); we merely want it to behave as if it's no longer active. All respectable databases will prevent something from being removed if it is being referred to (that's called referential integrity), but we don't want it to be removed even if nothing refers to it.
59
Open table as spreadsheet
Summary
Definition
Living entity last changed date and time
Every living entity shall store within it the date-and-time it was last changed.
This value shall be updated automatically each time the entity is modified, and it shall not be possible for it to be modified in any other way (such as by a user changing it explicitly).
Living entity last changed user ID
Every living entity shall store within it the user ID of the user who last changed it.
This value shall be updated automatically each time the entity is modified, and it shall not be possible for it to be modified in any other way (such as by a user changing it explicitly).
Living entity added date and time
Every living entity shall store within it the date and time it was added.
This value shall be set automatically when the entity is added and never modified thereafter.
Living entity added user ID
Every living entity shall store within it the user ID of the user who added it. This value shall be left empty for any entity that was added as a result of customer action (such as a customer entity resulting for the customer self-registering).
This value shall be set automatically when the entity is added and never modified thereafter.
Living entity change history
Every change to a living entity shall be recorded so as to build up a complete record of what values were changed, when, and by whom. Remove means
logical remove
Any living entity that is removed shall be logically removed only. The intent of this requirement is to allow details about any entity that has been removed to still be available when viewing historical data. For example, a report of user actions should still be able to show the names of employees who have departed.
Follow-on requirements (for a specific living entity) can also be written for any of the
first three kinds of pervasive requirement, regardless of whether a pervasive
requirement has been written on the same subject. A requirement can override any of the pervasive requirements by stating which of them does not apply to a particular living entity or class of living entities. Similarly, for any of these standard functions, a requirement can be written to describe features needed by a particular type of living entity (or class of living entities). This requirement would then override the standard function as specified in the pervasive requirement. If you do this, check that it's clear that only one function of each type is needed for each type of entity: you wouldn't
60
want developers to build one to satisfy the pervasive requirement and another for the specific requirement.
User Preferences
A user preference is an item of information that is set by a user to indicate one aspect of how they wish the system to behave. User preferences should be encouraged, because they improve users' experience of our system by discouraging a one-size-fits- all outlook. A requirement for a living entity that represents a class of users (for example, customers) can be followed by requirements that define user preferences (one requirement for each preference).
A requirement for a user preference should contain:
1. Name A unique, descriptive, and concise name for the preference.
2. User class(es) To which users does this preference apply?
3. Allowed values, or data type Let a user avoid making a choice if they don't
want to: let them choose "unspecified," "not applicable," or "I don't care," or for potentially impertinent information, "I don't wish to tell you."
4. Default value If the user doesn't set the value explicitly, what value will it
have? If you've defined a non-choice value (such as "unspecified"), make that the default.
Don't ask a user to express a preference that's not used (for example, because the piece of software that would use it hasn't been written yet). If someone realizes that
something they took the trouble to key in is ignored, they have a right to feel a little cheated.
It can also be worth writing one or more further requirement to ask for the ability to easily add extra preferences-at least to the extent that we don't have to modify the database structure each time-and perhaps a function for adding a user preference. Here are three requirements that define preferences:
Open table as spreadsheet Summary Definition Customer mailing list preference
A customer shall be able to indicate whether they wish to join the product mailing list, which periodically sends out emails about new products.
User time zone A user shall be able to specify the time zone in which they reside. Preferred
notification method(s)
A user shall be able to specify by which means they wish to be notified of events pertaining to them. They shall be able to specify different notification method(s) for each event severity level. For each severity level, they shall be able to nominate one or more of the available notification methods.
61
Open table as spreadsheet
Summary
Definition
This requirement does not concern itself with which events each user is notified of.
8, Considerations for Development
Even if no pervasive requirements have been specified for the topics discussed in the previous "Extra Requirements" section, you might regard some of them worth acting upon-simply as good practice.
9, Considerations for Testing
Check that add, modify, remove, and inquire functions exist for every living entity. There might be more than one function for each of these four things. A suitable range of tests needs to be prepared for each of these functions.
62
Phụ lục 2: Course Registration Requirements
1. Problem Statement
As the head of information systems for Wylie College you are tasked with developing a new student registration system. The college would like a new client-server system to replace its much older system developed around mainframe technology. The new system will allow students to register for courses and view report cards from personal computers attached to the campus LAN. Professors will be able to access the system to sign up to teach courses as well as record grades.
Due to a decrease in federal funding, the college cannot afford to replace the entire system at once. The college will keep the existing course catalog database where all course information is maintained. This database is an Ingres relational database running on a DEC VAX. Fortunately the college has
invested in an open SQL interface that allows access to this database from college‟s Unix servers. The legacy system performance is rather poor, so the new system must ensure that access to the data on the legacy system occurs in a timely manner. The new system will access course information from the legacy database but will not update it. The registrar‟s office will continue to maintain course information through another system.
At the beginning of each semester, students may request a course catalogue containing a list of course offerings for the semester. Information about each course, such as professor, department, and prerequisites, will be included to help students make informed decisions.
The new system will allow students to select four course offerings for the coming semester. In addition, each student will indicate two alternative
choices in case the student cannot be assigned to a primary selection. Course offerings will have a maximum of ten students and a minimum of three students. A course offering with fewer than three students will be canceled. For each semester, there is a period of time that students can change their schedule. Students must be able to access the system during this time to add or drop courses. Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester. If a course fills up during the actual registration process, the student must be notified of the change before submitting the schedule for processing.
At the end of the semester, the student will be able to access the system to view an electronic report card. Since student grades are sensitive
63
unauthorized access.
Professors must be able to access the on-line system to indicate which courses they will be teaching. They will also need to see which students signed up for their course offerings. In addition, the professors will be able to record the grades for the students in each class.
2. Glossary
2.1. Introduction
This document is used to define terminology specific to the problem domain, explaining terms, which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information.
2.2. Definitions
The glossary contains the working definitions for the key concepts in the Course Registration System.
2.3. Course
A class offered by the university.
2.4. Course Offering
A specific delivery of the course for a specific semester – you could run the