The document outlines the functional requirements for an article management system. It describes features for searching articles by author, category or keyword. It also describes functions for communicating, adding authors and reviewers, updating personal information, and assumptions about users. The requirements are translated into propositional calculus statements for the search, communicate, add, and update functions. Comments note challenges in translating natural language requirements to unambiguous mathematical statements.

1. ROZALIA BINTI
ALIK
A141963
TK8

2. 1.0 LOGICAL STRUCTURE OF THE DATA
The logical structure of the data to be stored in the internal Article
Manager database is given above.

3. 2.0 STATEMENTS OF
FUNCTIONAL REQUIREMENTS
OF THE SYSTEM.

4. SEARCH ARTICLE
 If the search is by Author, the system creates and presents
an alphabetical list of all authors in the database. In the case
of an article with multiple authors, each is contained in the
list.
 If the Reader selects to search by category, the system
creates and presents a list of all categories in the database.
 If the Reader selects to search by keyword, the system
presents a dialog box to enter the keyword or phrase.

5. COMMUNICATE
 If the user prefers to use his or her own email
directly, sufficient information will be contained on
the Web page to do so.

6. ADD AUTHOR
 Either field is blank, the Editor is instructed to add
an entry. No validation for correctness is made.

7. ADD REVIEWER
 If there is no entry for the email address in the HS
database or on this grid, the Editor will be
reprompted for an entry. No validation for
correctness is made.

8. UPDATE PERSON
 If any required field is blank, the Editor is instructed
to add an entry. No validation for correctness is
made.

9. 2.0NON-FUNCTIONAL
REQUIREMENTS

10.  The Online Journal will be on a server with
high speed Internet capability.
 The physical machine to be used will be
determined by the Historical Society.
 The software developed here assumes the
use of a tool such as Tomcat for connection
between the Web pages and the database.

11.  The speed of the Reader’s connection will
depend on the hardware used rather than
characteristics of this system.
 The Article Manager will run on the editor’s
PC and will contain an Access database.
 Access is already installed on this computer
and is a Windows operating system.

12. 3.O ASSUMPTIONS

13.  The Reader is expected to be Internet literate and
be able to use a search engine.
 The Author and Reviewer are expected to be
Internet literate and to be able to use email with
attachments.
 The Editor is expected to be Windows literate and
to be able to use button, pull-down menus, and
similar tools.

14. 2.0 THE MATHEMATICAL STATEMENTS
OF THE FUNCTIONAL REQUIREMENTS.
(PROPOSITIONAL CALCULUS)

15. SEARCH ARTICLE
Search_by_author : the search is by Author
system_creates : the system creates
present_alphabetical : presents an alphabetical list of all authors in the database.
Search_by_author -> system_creates^present_alphabetical
Reader_selects_by_category : the Reader selects to search by category
system_creates : the system creates
present_list_categories : presents a list of all categories in the database
Reader_selects_by_category -> system_creates^present_list_categories
Reader_search_keyword : the Reader selects to search by keyword
system_presents_dialog_box_enter_keyword : the system presents a dialog box to enter
the keyword
phrase : phrase
Reader_search_keyword -> system_presents_dialog_box_enter_keyword V phrase

16. COMMUNICATE
User_email_directly : the user prefers to use his or
her own email directly
sufficient_information : sufficient information ` will
be contained on the Web page to do so
User_email_directly -> sufficient_information

17. ADD AUTHOR
Field_blank : field is blank
editor_add_entry : the Editor is instructed to add an
entry
valid_correctness : No validation for correctness is
made.
 Field_blank  editor_add_entry.
 ~valid_correctness

18. ADD REVIEWER
entry_email : there is no entry for the email address in
the HS database or on this grid
Editor_reprompted : the Editor will be reprompted for
an entry
valid_correctness : No validation for correctness is
made.
 ~entry_email -> Editor_reprompted.
 ~valid_correctness

19. UPDATE PERSON
Field_blank : any required field is blank
editor_add_entry : the Editor is instructed to add an
entry.
valid_correctness : No validation for correctness is
made.
 Field_blank -> editor_add_entry.
 ~valid_correctness

20. 3.0 COMMENTS ABOUT THE TRANSLATION PROCESS
FROM NATURAL LANGUAGES STATEMENTS TO
MATHEMATICAL STATEMENTS.

21.  ambiguity:Natural languages are full of ambiguity, which
people deal with by using contextual clues and other
information. Mathematical statements are designed to be
unambiguous, which means that any statement has
exactly one meaning, regardless of context.
 redundancy:To make up for ambiguity and reduce
misunderstandings, natural languages are often
redundant. Mathematical statements are more concise.

22.  Statement :The meaning of a Mathematical
statements is unambiguous and literal, and can be
understood entirely by analysis of the tokens and
structure.
 literalness:Natural languages are full of idiom and
metaphor. Formal languages mean exactly what
they say.People who grow up speaking a natural
language (everyone) often have a hard time
adjusting to formal languages. In some ways the
difference between formal and natural language is
like the difference between poetry and prose, but
more so :