Technical Documentation Essay examples

Submitted By chuckaloci
Words: 2906
Pages: 12
Open Document
Technical Documentation – Test Planning:
Opening the database:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
1
Opening database

You will be asked to enter a password
2
Entering password
Correct: password
Main Menu will appear

Incorrect: pasword
Error message will appear

Switchboard:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
3
Main Menu opening

Main Menu appears automatically and is maximised
4
Customer Menu button

FrmCustomer Menu will open maximised
5
Employee Menu button

FrmEmployee Menu will open maximised
6
Order Button Menu

FrmOrder Menu will open maximised
7
Product Button Menu

FrmProduct Menu will open maximised
8
Supplier Button Menu

FrmSupplier Menu will open maximised
9
Report Button Menu

FrmReport Menu will open maximized

Form Customer:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
10
Add Customer Button

Add a Customer form appears maximised and opened at a blank record
11
Edit Customer Button

Asked to enter a Customer Number – if it matches with one in the database the correct record will appear, if not blank record will appear
12
Delete Customer Button

Asked to enter a Customer Number – if it matches with one in the database the correct record will appear, if not blank record will appear
13
Return to Main Menu button

Form Customer closes & Main Menu opens maximised

Form Employee:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
14
Add Employee Button

Add an Employee form appears maximised and opened at a blank record
15
Edit Employee Button

Asked to enter an Employee Number – if it matches with one in the database the correct record will appear, if not blank record will appear
16
Delete Employee Button

Asked to enter an Employee Number – if it matches with one in the database the correct record will appear, if not blank record will appear
17
Return to Main Menu button

Form Employee closes & Main Menu opens maximised

Form Order:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
18
Add Order Button

Add an Order form appears maximised and opened at a blank record
19
Edit Order Button

Asked to enter an Order Number – if it matches with one in the database the correct record will appear, if not blank record will appear
20
Delete Order Button

Asked to enter an Order Number – if it matches with one in the database the correct record will appear, if not blank record will appear
21
Return to Main Menu button

Form Order closes & Main Menu opens maximised

Form Product:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
22
Add Product Button

Add an Product form appears maximised and opened at a blank record
23
Edit Product Button

Asked to enter an Product Number – if it matches with one in the database the correct record will appear, if not blank record will appear
24
Delete Product Button

Asked to enter an Product Number – if it matches with one in the database the correct record will appear, if not blank record will appear
25
Return to Main Menu button

Form Product closes & Main Menu opens maximised

Form Supplier:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
26
Add Supplier Button

Add an Supplier form appears maximised and opened at a blank record
27
Edit Supplier Button

Asked to enter an Supplier Number – if it matches with one in the database the correct record will appear, if not blank record will appear
28
Delete Supplier Button

Asked to enter an Supplier Number – if it matches with one in the database the correct record will appear, if not blank record will appear
29
Return to Main Menu button

Form Supplier closes & Main Menu opens maximised

Form Report:
TEST NUMBER
TEST ITEM
TEST DATA
EXPECTED OUTCOME
30
Address Labels Button

RptAddressLabels will open in report view
31
Customer Invoice
Correct:
“1, 10/10/2014”
Incorrect:
“1,10/10/14”
Asked to enter a Customer Number and an Order Date – if the matching customer has placed an order that day their invoice will appear, if not a blank record will appear
32
Employee Wage Slip

RptEmployeeWageSlip I will open in
Show More

Related Documents: Technical Documentation Essay examples

Essay about Content and Importance of user and technical documentation

Content and Importance of user and technical documentation. The content & importance of the user documentation The user manual contains a lot of content. It shows who will be actually using the system or the main target audience. The user documentation will provide the user with a simple instructions manual or sheet which guides the user based upon their view on the system. This would need to simple as the users do not have the knowledge like the IT technicians, whereas the technicians would possibly have it in a programming language…

Words 408 - Pages 2

Technical Directive Compliance

Technical Directive Compliance The Navy and Marine Corps spend 81,025 man-hours incorporating 22,614 Technical Directive based maintenance actions in CY-16. With such an enormous effort associated with maintaining every asset in the inventory, why is there not a fully functional, accurate maintenance tracking system in place? Senior Leaders must ensure the proper incorporation and documentation of Aviation Technical Directives, as it assures fleet readiness, operational capability, and safety of…

Words 818 - Pages 4

What Are Some Of The Factors That Can Ensure More Success In The Sdlc Process

are some of the factors that can ensure more success in the SDLC process? Management Support, Technical and Business Expertise, Focal point Designation, Well defined procedures, Proper documentation for maintenance. Understand the ramifications of using and not using an SDLC approach. Advantages W/ SDLC: Clear idea what should/should not be built, goal is clear and can be on time. Proper documentation will help with maintenance. Disadvantages W/ SDLC: is the difference between what is written…

Words 546 - Pages 3

Development And Implementation Of Software

BSA375 Week 4 Lecture Development & Implementation of Software This lecture will examine several additional areas related the development and implementation of software. First of all many organizations must compare and evaluate the costs and schedule tradeoff of building an information system in house versus buying a vendor software product versus having a custom system built by contractors. A number of organizations continue to build their own software today but usually do not spend resources developing…

Words 1691 - Pages 7

Essay about BA Stage 2 Folio Checklist 14 15 1

the collection • Index of all items included in the collection • Technical requirements specific to the material nature of the collection .................................................................................................................................................... > Design process + development • Research and precedents • Sketches, drawings etc. of initial/ earlier versions • Photographic documentation of all development models .........................................…

Words 370 - Pages 2

case study Essay

unit. The management goal is to understand the causes of problems and investigate possible call flow redesign options. Submission requirements: Deadline: Thursday March 13th 2014 Individual management report [15% of the marks for the Unit] Technical report/appendices + computer files (one per team) [20% of the marks for the Unit] Team presentations [15% of the marks for the Unit] See later for more detail. Introduction Delwarca’s Remote Support unit is under pressure due to inefficiencies…

Words 937 - Pages 4

BSA375 Week Two Essay

limited to documentation, interviews, observation, questionnaires, and statistical measurements. Gathering information via documentation can take many different forms. One form of gathering information via documentation is to review the history of the current information systems project or the business problem to be addressed if there is not an existing information system. This can be accomplished by reading prior project correspondence files, system documentation, project documentation, internal…

Words 1349 - Pages 6

Bound Together Are We Allies Or Enemies

Bound together: Are we allies or enemies? As both author and editors share the goal of creating accurate and usable documentation, one might think they would naturally work in harmony. Walking through the literature on author-editor relationships, however, a different picture is painted. Indeed, the author-editor relationship is often cast in an “adversarial” light (Grove, 1990), featuring the two players in a battle for authority over the work. Authors are depicted as sensitive, sulky, defensive…

Words 498 - Pages 2

Hrm 531 Week 4 Testing Business Plan

to complete technical system testing to ensure the expected performance and functional results are successful without errors being present. In addition to the technical testing, user acceptance testing will be designed within test case scenarios where user input will be required for the formulation of the test case creation. It is a requirement that…

Words 995 - Pages 4

Essay Patent Databases

service overall. Please rate ABC's customer support overall. Please rate ABC's technical product training courses overall. Please rate ABC's documentation overall. Overall, how satisfied are you with ABC's customer service? Overall, how satisfied are you with ABC's customer support? Overall, how satisfied are you with ABC's customer technical product training courses? Overall, how satisfied are you with ABC's documentation? In addition, reference and retention questions may be added. Examples How…

Words 1521 - Pages 7