Professional software architect wanted.
I am only looking for for professionals with prove of this.
This project involves making a booking system that can work together from different webpages. Collect the products and spit them them out in different ways relating to online users requirements like: Rating, popularity, etc.
The projects details will be discussed with me also relating to future development.
WHAT HAVE TO BE PLANNED:
1. Input Descriptions (to collect data or request
an output) - be it implemented by a GUI, command line
interface, verbal, optical, or through some other screen
interface. All inputs should include:
a. Name, alternate ID, program label, description.
b. Defined layout and examples.
c. Input transaction specifications, including default
values and editing rules for data to be collected.
d. Messages; e.g., data validation, and general processing.
e. Panels (for screens).
f. Relationship of inputs to outputs.
2. Output Descriptions (to retrieve data) - be it implemented
by a GUI, printed report, audio/video, or through some other
screen interface. All outputs should include:
a. Name, alternate ID, program label, description.
b. Defined layout and examples.
c. Panels (for screens), maps (for reports).
d. Messages; e.g., general processing and program specific
information/warning/error messages.
3. Data Structure Descriptions (data bases, files, records,
and data elements).
a. All data structures should include: Name, alternate ID,
program label, description. They should also include...
b. Data Bases - organization, key(s), labels, volume/size,
backup requirements, internal structure.
c. Files (both primary and working) - organization, key(s),
labels, volume/size, backup requirements, internal structure,
file-to-file relationships.
d. Records - form, length, key(s), contents, record-to-record
relationships.
e. Data Elements - class, justification, fill character,
void state, mode, picture, label, size, precision, scale,
validation rules. If generated data, rules for calculation.
If group data, rules for assignment.
4. Program Description:
a. Name, alternate ID, program label, description.
b. Characteristics: Required processing speed, memory
requirements.
c. Dependencies to other programs externally (e.g.,
batch job stream).
d. Dependencies to modules internally (e.g., DLLs,
subroutines, etc.)
e. Functions to be performed with Inputs, Outputs, and
Data Structures (create/update/reference).
f. Special processing rules (logic for processing)
g. Command language required to execute the program
(e.g., command files, JCL, etc.)
h. Physical environment where program will be executed.
i. Test Plan and how to assemble test data.
j. Method of implementation - programming language(s) to
be used, design techniques to be observed, tools to be
used.