ROZALIA BINTI

ALIK

A141963

TK8

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.

2.0 STATEMENTS OF

FUNCTIONAL REQUIREMENTS

OF THE SYSTEM.

SEARCH ARTICLE

If the search is by Author, the system creates and presents an alphabetical list of all authors in the database

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.

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.

ADD AUTHOR

Either field is blank, the Editor is instructed to add

an entry. No validation for correctness is made.

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.

UPDATE PERSON

If any required field is blank, the Editor is instructed

to add an entry. No validation for correctness is

made.

3.0NON-FUNCTIONAL

REQUIREMENTS

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.

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.

4.O ASSUMPTIONS

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.

5.0 THE MATHEMATICAL STATEMENTS

OF THE FUNCTIONAL REQUIREMENTS.

(PROPOSITIONAL CALCULUS & PREDICATE

CALCULUS)

SEARCH ARTICLE

PROPOSITIONAL CALCULUS

Search_by_author : the search is by Authorsystem_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

PREDICATE CALCULUS

Search(author) : the search is by Author

system(creates) : the system creates

alphabetical(present,authors) :presents an alphabetical list of all authors in the database

Search(author) => system(creates)^ alphabetical(present,authors)

Search(reader_selects,category): the Reader selects to search by

category

creates(system): the system creates

categories(present,database):presents a list of all categories in the

database.

Search(reader_selects,category)=>creates(system)^categories(present,database)

COMMUNICATE

PROPOSITIONAL CALCULUS

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

PREDICATE CALCULUS

Use(user_prefers,email_directly): the user prefers to use his or her own email directly contained(sufficient_information,webpage): sufficient information will be contained on the Web page to do so

Use(user_prefers,email_directly)=>contained(sufficient_information,webpage)

ADD AUTHOR

PROPOSITIONAL CALCULUS

Field_blank : field is blankeditor_add_entry : the Editor is instructed to add an entryvalid_correctness : No validation for correctness is made.

Field_blank editor_add_entry.

~valid_correctness

PREDICATE CALCULUS

blank(field) : Either field is blank

add(editor_instructed) : the Editor is instructed to add

an entry

correctness(~valid) : No validation for correctness is

made

blank(field) add(editor_instructed).

correctness(~valid)

ADD REVIEWER

PROPOSITIONAL CALCULUS

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

PREDICATE CALCULUS

email_address(~entry,database)^grid : there is no entry for the email address

in the HS database or on this grid

reprompted(entry) : there is no entry for the email address in the HS database

or on this grid

email_address(~entry,database)^grid=>reprompted(entry)

Correctness (~valid)

UPDATE PERSON

PROPOSITIONAL CALCULUS

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

PREDICATE CALCULUS

Blank(required_field): any required field is blank instructed(editor,add_entry): the

Editor is instructed to add an entry

Correctness (~valid) : No validation for correctness is made.

Blank(required_field)=> instructed(editor,add_entry)

Correctness (~valid)

6.0 COMMENTS ABOUT THE TRANSLATION PROCESS

FROM NATURAL LANGUAGES STATEMENTS TO

MATHEMATICAL STATEMENTS.

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.

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 .