twrs d. - digital library/67531/metadc685915/m2/1/high... · whc-sd-wm-sdr-011 rev. 0 1 .o...

2. To: (Receiving Organization) 3. Frm: ( O r i g i n a t i n g Organization) 4. Related ED1 No.:

D i s t r i b u t i o n TWRS SE R isk Management & N/A Model i ng

5. P r o j ./Prog./Dept ./Div. : 6. Design A u t h o r i t y 1 Design Agentlcog. 7. Purchase Order No.: Engr.:

TWRS D. D. Frank

Document t r a n s m i t t e d f o r re lease. a. o r i g i n a t o r Remarks: 9. Equip.lConponent No.:

10. System/Bldg./Facility:

12. Major Assm. Dug. No.: 11. Receiver Remarks: 11A. Design Baseline Docunent? [ ] Yes [ X I NO

13. P e r m i t l P e r n i t A p p l i c a t i o n No.:

15. DATA TRANSMITTED ( F ) Approval

Desio. IEI Title or Description of Data IAI IC1 ID1 Rev'

NO NO. NO. Transmitted nator IBI DocumontlDrawing No.

1 WHC-SD-WM-SDR-011 0 Requirements N/A Management System Browser Software Requirements S p e c i f i c a t i o n

Reason Origi- tor . nator

Trans- Dispo- mittal sition

I I I 16. KEY

Appmval Dseignator IF1 Reason for Tranmiffal IGI Disposition IHI & Ill 1. Appmval 4. Review 1. Approved 4. Rwiswsd nalmmmant E. S. (1. D or NlA

1s.. WHC-CM-3-5. 2. Rslaars 5. Post-Review 2. Approved wlcomment 5. Reviewed wlmmmant Ssc.12.71 3. Information 6. Dirt. (Receipt Acknow. Required1 3. Disapproved wlcomment 6. Receipt acknowledged

17. SlGNATURElDlSTRlBUTlON lSsa Appmval Designator far required agnaturoBl

IGI 101 IHI R ~ ~ . I d2L I IJI Name IKI Signature ILI Date IMI MSlN I R ~ ~ . I DisD, I IJI Name IKI Signature ILI Data IMI MSlN

QA

I 1 Safety

Env.

la. I 19. I 20. 21. DOE APPROVAL ( i f required) C t r l . No.

I1 Approved [I Approved u l c m n t s [I Disapproved u / c m n t s

Cognizant Manager

d j % 4 0 ) d q/SO[?b Signature of EDT Date Authorized Rsprassntative Date Originator tor Receiving Organization

80-7400-1 72-1

WHC-SD-WM-SDR-011, Rev. 0

Requirements Management System Browser Software Requirements Specification

D. D. Frank, B. C. Gne i t i ng Westinghouse Hanford Company, Rich1 and, WA 99352 U.S. Department o f Energy Contract DE-AC06-87RL10930

EDT/ECN: 618218 UC: 905 Org Code: 74400 Charge Code: DlMlM B&R Code: EW3120075 To ta l Pages: 1 3

Key Words: systems engineering, requirements management, RMSB, RMACS, browser, parser , SE t o o l s .

Abs t rac t : The purpose o f t h i s document i s t o d e f i n e t h e e s s e n t i a l user requi rements f o r t h e Requirements Management System Browser (RMSB) a p p l i c a t i o n . Th is i nc ludes s p e c i f i c a t i o n s f o r t h e Graphica l User I n t e r f a c e (GUI) and t h e suppor t ing database s t ruc tu res . The RMSB a p p l i c a t i o n i s needed t o p rov ide an easy t o use PC-based i n t e r f a c e t o browse system engineer ing data s to red and managed i n a UNIX sof tware a p p l i c a t i o n . The system engineer ing data i nc lude func t i ons , requirements, and a r c h i t e c t u r e s t h a t make up the Tank Waste Remediation System (TWRS) techn ica l base1 ine . Th is document a l s o covers t h e requi rements f o r a sof tware a p p l i c a t i o n t i t l e d "RMSB Data Loader (RMSB- DL)", r e f e r r e d t o as t h e "Parser." The Parser i s needed t o read and parse a da ta f i l e and l o a d t h e data s t r u c t u r e suppor t ing t h e Browser.

TRADEMARK DISCLAIMER. t rade name, tradenark, manufacturer, o r otheruise, does not necessar i ty c o n s t i t u t e o r i n p l y i t s endorsement, r e c m n d a t i o n , o r f avo r ing by the Uni ted States G o v e r m n t o r any agency thereof o r i t s con t rac to rs o r subcontractors.

Reference he re in t o any s p e c i f i c c m r c i a l product, process, o r se rv i ce by

P r i n t e d i n the Uni ted States of America. To ob ta in copies of t h i s docunent, contact: UHC/BCS DocMent Control Services, P.O. Box 1970. Mai ls top H6-08, Richland UA 99352, Phone (509) 372-2420; Fax (509) 376-4989.

\

1. Y Release Approval

Approved for Public Release

A-6400-073 (10/95) GEF321

WHC-SD-WM-SDR-011 Rev . 0

CONTENTS

1 . 0 INTRODUCTION . . . 2 . 0 PURPOSE AND SCOPE . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. 1

. 1

3 . 0 ABBREVIATIONS AND ACRONYMS . . . . . . . . . . . . . . . . . . . . . 2

4 . 0 REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 . 1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 . 2 PARSER FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . 3 4 . 3 DATABASE STRUCTURE . . . . . . . . . . . . . . . . . . . . . . 3 4 . 4 GRAPHICAL USER INTERFACE . . . . . . . . . . . . . . . . . . . 4

4 . 4 . 1 General . . . . . . . . . . . . . . . . . . . . . . . . 4 4 . 4 . 2 Main Window . . . . . . . . . . . . . . . . . . . . . . 5 4 . 4 . 3 User Pre ferences Window . . . . . . . . . . . . . . . . 6 4 . 4 . 4 Record E d i t i n g Window . . . . . . . . . . . . . . . . . 6 4 . 4 . 5 Element R e l a t i o n s h i p Window . . . . . . . . . . . . . . 7 4 . 4 . 6 Change Window . . . . . . . . . . . . . . . . . . . . . 8 4 . 4 . 7 Search Window . . . . . . . . . . . . . . . . . . . . . 8 4 . 4 . 8 Add R e l a t i o n s Window . . . . . . . . . . . . . . . . . . 9 4 . 4 . 9 Change H i s t o r y Window . . . . . . . . . . . . . . . . . 9

4 . 5 OTHER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . 10

5 . 0 OTHER CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . . . . . 11

6 .0 REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

ii

WHC-SD-WM-SDR-011 Rev. 0

1 .O INTRODUCTION

Systems Engineer ing i n fo rma t ion f o r t he Tank Waste Remediation System (TWRS) i s c u r r e n t l y s to red and managed w i t h the RDD-100' sof tware a p p l i c a t i o n . eng inee r ing process i n c l u d i n g func t i ons , requirements, and a r c h i t e c t u r e d e f i n i t i o n s f o r s p e c i f i c a t i o n s . The RDD-100 a p p l i c a t i o n runs on a UNIX works ta t i on , cos ts over S30K per l i cense , and i s n o t an open system. Therefore, a personal-computer (PC)-based system i s needed t o increase t h e a b i l i t y o f engineers and managers on -s i t e t o access and modi fy t h e i n f o r m a t i o n s to red i n t h e RDD-100 system. access t o t h e RDD-100 data f o r a wide range o f users, a r e l a t i o n a l database w i t h a g raph ica l user i n t e r f a c e (GUI ) i s requ i red f o r PC users runn ing M i c r o s o f t Windows. Th is sof tware a p p l i c a t i o n w i l l be t i t l e d , "Requirements Management System Browser" (RMSB) o r "Browser".

The Browser data s t r u c t u r e and i n t e r f a c e des ign must c l o s e l y mimic t h e RDD-100 da ta s t r u c t u r e and terminology. The suppor t ing database t a b l e s f o r t h e Browser s h a l l match each element t ype i n RDD-100 and t h e r e l a t i o n s h i p s between elements s h a l l be recorded i n a t a b l e named a f t e r t h e RDD-100 r e l a t i o n s h i p . To t r a n s f e r data from RDD-100 t o the Browser, a PC-based GUI s h a l l be developed w i t h t h e t i t l e - RMSB Data Loader (RMSB-DL) o r t h e "Parser" . l o a d t h e RMSB database.

The RDD-100 a p p l i c a t i o n manages data suppor t i ng t h e systems

To p rov ide a more open and c o s t - e f f e c t i v e

The Parser i s requ i red t o read and parse an RDD-100 .RDT f i l e and

2.0 PURPOSE AND SCOPE

The purpose o f t h i s document i s t o i d e n t i f y t h e sof tware requi rements f o r t h e RMSB a p p l i c a t i o n . s t r u c t u r e s and t h e GUI. The d e s c r i p t i o n con ta ins s u f f i c i e n t d e t a i l t o desc r ibe t h e processes used by t h e sof tware. t h e RMSB i n s t a l l a t i o n software, o r t he RMSB updat ing sof tware. and update o f t h e RMSB a p p l i c a t i o n i s covered i n t h e documentation f o r t h e TWRS Systems Engineer ing Tools gener i c i n s t a l l a t i o n program and gener i c automat ic update sof tware. TWRS Systems Engineer ing Software Con f igu ra t i on Management Plan (WHC-SD-WM-CSCM-034) f o r t h e TWRS Systems Engineering Tools .

Th i s i nc ludes a s p e c i f i c a t i o n o f t h e database

Th is document does n o t i n c l u d e I n s t a l l a t i o n

Revis ions o f t he sof tware are covered by t h e d r a f t

'RDD-100 i s a r e g i s t e r e d trademark o f Ascent Logic Corporat ion

1


3.0 ABBREVIATIONS AND ACRONYMS

The t a b l e below i d e n t i f i e s and de f i nes t h e abbrev ia t i ons and acronyms

ERA Element-Relat ion-At t r ibute, t he database model used by

GU I Graphical User I n t e r f a c e RMACS RMSB Requirements Management System Browser, t h e Browser RMSB-DL RMSB Data Loader, t he Parser SE Systems Engineer ing SQL S t ruc tu red Query Language TWRS Tank Waste Remediation System

used w i t h i n t h i s document.

RDD-100

Requirements Management and Assured Compliance System

4.0 REQUIREMENTS

The f o l l o w i n g sec t i ons i d e n t i f y sof tware requirements f o r t h e development o f t h e RMSB a p p l i c a t i o n . The requirements are grouped i n t o f i v e sec t i ons : 1) o v e r a l l o r general requirements f o r t he app l i ca t i on ; 2) requirements f o r t h e u t i l i t y t h a t parses an RDD-100 data f i l e and loads t h e RMSB database; 3) requi rements f o r t he database s t r u c t u r e con ta in ing t h e data; 4) t h e g raph ica l user i n t e r f a c e requirements organized by main f u n c t i o n a l i t y groups (windows); and 5) o t h e r requirements t h a t are n o t covered i n t h e o t h e r f o u r areas.

4 . 1 GENERAL

Th is s e c t i o n descr ibes t h e h igh - leve l f u n c t i o n a l requirements r e q u i r e d f o r t h e PC-based sof tware system. The miss ion o f t h i s system i s t o p rov ide a cos t e f f e c t i v e way f o r a wide spectrum o f users t o view t h e TWRS t e c h n i c a l base l i ne da ta s to red i n RDD-100 and moni tor changes between r e v i s i o n s . b r i d g e t o RDD-100 in fo rma t ion should a l so p rov ide a p l a t f o r m f o r o t h e r a p p l i c a t i o n s t o ga in access t o t h e system engineer ing da ta s to red i n RDD-100.

Th is

1. The a p p l i c a t i o n must run on a PC and have a M i c r o s o f t Windows t ype g raph ica l user i n t e r f a c e t h a t operates e f f i c i e n t l y i n t h e windows environment.

2 . The i n t e r f a c e must use windows, but tons, menus, s c r o l l bars, mouse- c l i c k events, and o the r windows c o n t r o l s t o manipulate t h e user ’s view o f t h e data and t o nav igate through t h e data, i . e . , a simple, easy t o use, po in t -and -c l i ck i n t e r f a c e .

The database engine s t o r i n g the RDD-100 data must suppor t t h e S t ruc tu red Query Language (SQL) and the PC windows environment.

The system must be ab le t o read an RDD-100 da ta f i l e (.RDT f i l e ) , parse ou t t h e requ i red data, and download t h e i n f o r m a t i o n i n t o a PC database s t r u c t u r e .

2.

3 .

2


4. The database must be s t r u c t u r e d so t h a t i t mimics t h e RDD-100 schema and terminology t o p rov ide system commonality and ease o f da ta t r a n s f e r .

The g raph ica l user i n t e r f a c e and database s t r u c t u r e must suppor t t h e user a c t i v i t i e s o f browsing, s o r t i n g , searching (da ta que r ies ) , mon i to r i ng changes between data sets , and a l l o w i n g e l e c t r o n i c capture and upload o f se t o f proposed da ta changes made by t h e user .

5.

4.2 PARSER FUNCTIONS

A so f tware t o o l i s requ i red t o i n i t i a l l y conver t t h e RDD-100 in fo rma t ion , i n t h e form o f an .RDT f i l e , i n t o the database s t r u c t u r e t h a t w i l l be used by t h e Browser (See Sect ion 4.3). r e q u i r e d t o per form t h e f o l l o w i n g func t i ons :

1. Create t h e database s t r u c t u r e .

2. Parse an .RDT f i l e generated by RDD-100, i n c l u d i n g t h e a b i l i t y

Th is t o o l , t i t l e d RMSB-DL o r Parser i s

t o f i l t e r ou t and igno re those elements, r e l a t i o n s , and a t t r i b u t e s n o t de f i ned f o r t h e TWRS database s t r u c t u r e .

3 . Parse the change h i s t o r y i n fo rma t ion i n t h e .RDT f i l e .

4. Generate a reco rd count r e p o r t f o r a l l element and r e l a t i o n t a b l e s .

A l l ow the user t o en te r a 250 cha rac te r name o r d e s c r i p t i o n f o r t h e da ta s e t be ing parsed.

5.

4.3 DATABASE STRUCTURE

The f o l l o w i n g requirements apply t o t h e database s t r u c t u r e f o r t h e Browser and t h e Parser app l i ca t i ons . s t r u c t u r e conform t o t h e schema used w i t h i n ROD-100. R e l a t i o n - A t t r i b u t e (ERA) s t r u c t u r e , where elements rep resen t records o f va r ious types, t he a t t r i b u t e s are t h e " f i e l d s " o r data values o f each element record, and r e l a t i o n s are used t o i d e n t i f y l i n k s between elements.

These requirements on t h e database RDD-100 uses an Element-

1. There s h a l l be one t a b l e f o r each element t ype used w i t h i n RDD- 100. t a b l e s t r u c t u r e . Requirements, A rch i tec tu res , and so on.

2. A l t e r n a t e (RMACS and RDD-100) nomenclature f o r t h e elements, a t t r i b u t e s , and r e l a t i o n s s h a l l be prov ided.

3 . A l l o f t h e necessary a t t r i b u t e s associated w i t h each element t ype c u r r e n t l y used w i t h i n t h e RDD-100 database, i n c l u d i n g t h e element t ype (S t r i ng , I n tege r ) and s i z e (bytes) s h a l l be re ta ined .

Elements o f t h e same t ype s h a l l be conta ined i n a s i n g l e Example o f element types i n c l u d e Functions,

3


4 .

5 .

6 .

7 .

8.

9.

A l l o f t h e r e l a t i o n s c u r r e n t l y used by RDD-100 s h a l l be re ta ined . Each r e l a t i o n s h a l l be conta ined i n i t s own t a b l e , and i d e n t i f y t h e source and t a r g e t elements f o r t h e r e l a t i o n .

The data and suppor t ing s t r u c t u r e s h a l l be mainta ined i n a database engine t h a t runs on a PC i n t h e windows environment.

Element records s h a l l be indexed by the "Name" a t t r i b u t e , o r "Number" and "Name" a t t r i b u t e s .

R e l a t i o n records s h a l l be indexed by t h e source element t ype and name, and by the t a r g e t element t ype and name.

Change h i s t o r y i n fo rma t ion f o r elements, r e l a t i o n s , and a t t r i b u t e s s h a l l be r e t a i n e d i n the database s t r u c t u r e .

Change h i s t o r y i n f o r m a t i o n s h a l l be indexed by the element t y p e and element name.

4.4 GRAPHICAL USER INTERFACE

4.4.1 General

The f o l l o w i n g are requirements f o r t he o v e r a l l des ign and development o f t h e GUI f o r t h e Browser sof tware. Because t h e Parser w i l l n o t be d i s t r i b u t e d , these requi rements do n o t apply t o t h e Parser. are g e n e r a l l y broken down i n t o s p e c i f i c groupings o f f u n c t i o n s conta ined i n an o b j e c t c a l l e d a window.

The f u n c t i o n a l requi rements

1.

2.

3 .

4 .

5.

6 .

Any window w i t h i n t h e sof tware t h a t con ta ins t e x t i n p u t f i e l d s s h a l l have an " E d i t " menu w i t h t h e standard "Cut and Paste" c a p a b i l i t i e s . These func t i ons s h a l l exchange data w i t h t h e Windows c l i pboard , which can then exchange t h e da ta w i t h o t h e r Windows a p p l i c a t i o n s .

Wherever poss ib le , a l l menu i tems and c o n t r o l s (but tons, l i s t boxes, check boxes, e t c . ) s h a l l have keyboard equ iva len ts .

When poss ib le , any n o n - t r i v i a l windows s h a l l have r e s i z i n g c a p a b i l i t i e s , so t h a t t he c o n t r o l s i n those windows w i l l be s i z e d a p p r o p r i a t e l y when the window i s r e s i z e d by t h e user. Th i s w i l l a l s o sca le t h e window and c o n t r o l s t o f i t on any s i z e screen r e s o l u t i o n .

Resizable windows s h a l l have a minimum s i z e so t h a t c o n t r o l s do n o t ove r lap and t h e window i s s t i l l readable.

Resizable windows s h a l l i n i t i a l l y be f u l l screen f o r any screen r e s o l u t i o n g r e a t e r than o r equal t o VGA (640 by 480 p i x e l s ) .

A l l windows must be ab le t o f i t i n a minimum s i z e o f a VGA mon i to r ( 6 4 0 by 480 p i x e l s ) .

4


7. For any n o n - t r i v i a l windows, a "Help" menu must be a v a i l a b l e w i t h i n fo rma t ion about general t o p i c s and t h e c u r r e n t window as w e l l .

8. Windows t h a t con ta in t a b l e s o f element records s h a l l have a "double-c l ick ' ' event assoc iated w i t h them t h a t w i l l d i s p l a y t h e d e t a i l e d i n f o r m a t i o n on the se lected element record.

9. For any window w i t h n o n - t r i v i a l i n fo rma t ion , t h e a b i l i t y t o p r i n t t h e i n fo rma t ion must be prov ided.

4.4.2 Main Window

main window s h a l l be the i n i t i a l window d i sp layed by t h e a p p l i c a t i o n p r o v i d i n g t h e s t a r t i n g p o i n t f o r t h e sof tware f u n c t i o n a l i t y .

The Main window s h a l l :

The f o l l o w i n g requirements apply t o the main window o f t he Browser. The

1.

2.

3 .

4 .

5 .

6 .

7.

a. 9.

10

Disp lay t h e "Number" and "Name" a t t r i b u t e s f o r t h e records o f a user-se lected element t a b l e and p rov ide the user w i t h e t h e c a p a b i l i t y t o s e l e c t t h e element t ype t o d i s p l a y from t h e main window . H i g h l i g h t element records i n t h e main window t a b l e t h a t have been added, modi f ied, o r de le ted us ing va r ious c o l o r s .

Prov ide t h e a b i l i t ; t o s e l e c t whether t o s o r t t h e main window t a b l e by t h e "Name o r "Number" f i e l d .

D isp lay t h e d e t a i l e d reco rd i n fo rma t ion f o r any reco rd "double- c l i c k e d " i n the main window t a b l e . I f t h e reco rd i s one t h a t was deleted, a message box s h a l l d i s p l a y an e r r o r message t o t h e user . The in fo rma t ion s h a l l be d i sp layed i n a "Record E d i t i n g Window" descr ibed i n Sect ion 4.4.4.

Prov ide t h e a b i l i t y t o open any Browser database f i l e .

Prov ide t h e a b i l i t y t o expor t t h e c u r r e n t change i n f o r m a t i o n i n t o an .RDT f i l e readable by RDD-100, or t o an ASCII t e x t f i l e .

Prov ide access t o a preferences window t h a t a l l ows t h e user t o s e t va r ious user preferences.

Prov ide a mechanism f o r e x i t i n g the program.

Prov ide a mechanism f o r accessing a r e l a t i o n t a b l e s window.

Prov ide a mechanism f o r accessing an o l d views window.

5


11. Have a mechanism for adding and deleting element records in the current tab1 e.

Have a mechanism for accessing various query windows.

Have a mechanism for accessing a database changes windows.

Provide access to On-Line Help information.

12.

13.

14.

15. Be resizable.

4.4.3 User Preferences Window

A preferences window shall be used to set various user defined options for the software. The window must be accessible from the main window of the software

1.

2.

3.

4.

5.

6.

The preferences window shall provide the user with the ability to:

Select and customize element views for the record editing wi ndow . Select the nomenclature (labels) used by the Browser as either RDD-100 or RMACS names.

Select when justifications for changes to the data are made.

Cancel changes to the user's preferences.

Save the user's preferences to an initialization (.INI) file when exiting the window.

Provide on-line help.

4.4.4 Record Editing Window

on an element record. This includes any and all of the attributes of the element, and any relations from the element to other elements. be able to add, modify, and delete information from this window as well. Access to this window shall be by "double-clicking'' on an element record reference located in other windows, including the main and search windows.

The record editing window shall:

A Record Editing Window shall be used to display the detailed information

The user must

1. Display all or a selected set of attributes for an element type as defined by the user in the Preferences window.

2. Display any or all relations to other element records in the database.

3. Allow the user to modify and save changes to the attributes.

6

WHC-SD-WM-SOR-011 Rev. 0

4 .

5 .

6 .

7.

8.

9.

1 0 .

1 1 .

12.

Allow the user to add a new element of the same type or delete the current element record.

Provide a mechanism that adds or removes relationship links to other elements.

Provide record navigation capabilities that navigate through records in the current element table.

Provide a method of canceling changes made to the attributes of the current element record.

Provide a mechanism for returning to the previously viewed element . Provide a mechanism for accessing an old views window.

Provide a mechanism for viewing the change history information for the current element.

Provide access to on-line help for the window and current element type.

Be resizable.

4.4.5 Element Relationship Window

records in any one of the relation tables in the data structure. relations window shall be accessible from the program's main window and have the following functionality:

An element relationship or relations window shall be used to display the The

1. Display the element type, name, and number for the source and

2.

target elements for a user-selected relationship type.

Provide a selection box for changing the relationship type being viewed . Display the detailed record information for any source or target element "double-cl icked" in the table.

Have on-line help available for the window.

3 .

4 .

5 . Able to exit from the window.

6 . Be resizable.


4.4.6 Change Window

A change window s h a l l be developed t o d i s p l a y a summary o f t h e changes fo r elements, r e l a t i o n s , o r a t t r i b u t e s . D e t a i l e d i n f o r m a t i o n windows s h a l l be developed t o d i s p l a y t h e s p e c i f i c s f o r each t ype o f change. Note t h a t t h i s i s d i f f e r e n t from t h e change h i s t o r y windows, which s h a l l show t h e h i s t o r y o f changes t o t h e master RDD-100 database. d i s p l a y i n g t h e change i n f o r m a t i o n s h a l l be access ib le from the main window.

The change window(s) s h a l l :

The windows t h a t are used f o r

1. A l l ow t h e user t o s e l e c t which changes t o d i s p l a y i n t h e t a b l e , e i t h e r elements, r e l a t i o n s , o r a t t r i b u t e s .

Prov ide t h e a b i l i t y t o "double-c l ick ' ' on any change reco rd i n t h e main change window and d i s p l a y t h e d e t a i l e d i n f o r m a t i o n f o r t h e se lected change record. The window used t o d i s p l a y t h i s i n f o r m a t i o n w i l l depend on t h e change t a b l e be ing viewed.

A l l ow t h e user t o modi fy o n l y t h e j u s t i f i c a t i o n f i e l d i n t h e d e t a i l e d change windows; a l l o the r f i e l d s s h a l l be a u t o m a t i c a l l y entered when t h e change i s made.

2.

3 .

4. A l l ow t h e user t o e x i t each window.

5. Prov ide on - l i ne help.

6. Al low t h e user t o r e s i z e t h e main change window.

4.4.7 Search Window

The browser sof tware s h a l l p rov ide one o r more windows f o r search ing through t h e va r ious element t a b l e s based on t h e values o f t h e a t t r i b u t e s o r r e l a t i o n s . The user s h a l l be ab le t o s e l e c t an i ns tance from t h e search r e s u l t and view t h e d e t a i l e d i n fo rma t ion . The search windows s h a l l be access ib le from t h e main window o f t he sof tware.

The search window(s) s h a l l :

1. A l l ow t h e user t o query on records i n a se lec ted element t a b l e based on the a t t r i b u t e s and/or r e l a t i o n s associated w i t h t h e e l ement s . D isp lay a summary o f a l l o f t he records found f o r t h e c u r r e n t search c r i t e r i a .

2.

3 . D i sp lay t h e d e t a i l e d element reco rd i n fo rma t ion when a user

4.

"double-c l i c k s " on t h a t reco rd o f t h e r e s u l t s .

Prov ide a method o f c l e a r i n g t h e search r e s u l t s and s t a r t i n g over.

8


5. Provide a mechanism f o r e x i t i n g the windows.

6 . Provide On- l ine help.

4.4.8 Add Re la t i ons Window

An add r e l a t i o n s window s h a l l be developed t h a t p rov ides t h e user t h e a b i l i t y t o s e l e c t and add r e l a t i o n s from a source element t o one o r more t a r g e t elements. e d i t i n g window.

The add r e l a t i o n s window s h a l l :

The add r e l a t i o n s window s h a l l be access ib le from t h e reco rd

1.

2.

3 .

4 .

5.

6.

7.

Al low t h e user t o s e l e c t a t a r g e t element t ype f o r adding re1 a t i ons . A l l ow t h e user t o s e l e c t a s p e c i f i c r e l a t i o n when more than one r e l a t i o n i s used between t h e c u r r e n t element t ype and t h e se lec ted t a r g e t element type.

A l l ow t h e user t o s e l e c t one o r more elements t o add as t h e t a r g e t s o f t he se lec ted element r e l a t i o n s h i p .

Prov ide a means o f cance l i ng a r e l a t i o n s h i p a d d i t i o n .

Prov ide a means o f e x i t i n g the window and adding a r e l a t i o n .

Have on - l i ne Help.

Be r e s i z a b l e .

4.4.9 Change H i s t o r y Window

Change h i s t o r y windows s h a l l be developed t o d i s p l a y any o f t h e changes associated w i t h an element record. The change h i s t o r y w i l l be an a rch i ve of a l l o f t h e changes made t o the master RDD-100 base l i ne s ince t h e f i r s t r e v i s i o n . The windows s h a l l a l l o w the user t o compare va r ious vers ions of t e x t a t t r i b u t e s and i d e n t i f y t he d i f f e rences . Note t h a t t h i s i s d i f f e r e n t from t h e change windows, which d i s p l a y o n l y t h e changes t o the c u r r e n t da ta se t . window.

The change h i s t o r y window(s) s h a l l :

a c u r r e n t element record.

The change h i s t o r y windows s h a l l be access ib le from t h e reco rd e d i t i n g

1. D isp lay a l l o f t he element, a t t r i b u t e , and r e l a t i o n changes t o

2. A l l ow t h e user t o s e l e c t any vers ions o f an a t t r i b u t e va lue from the h i s t o r y f o r comparison.

9


3. Display "redline" formatted text to identify the differences between previous versions of the,,data set for text values. user must be able to print this

Have a mechanism for exiting the windows.

Have on-line Help information available.

The redline" text information.

4.

5.

6. Be resizable.

4.5 OTHER REQUIREMENTS

This section contains miscellaneous requirements that do not fall into one of the four categories above.

1.

2.

3.

4 .

5 .

6 .

7 .

8.

9.

Changes to the database information shall be verified for correctness before they are allowed. Example: A "Name" attribute may not be blank, a "Number" attribute must be in the correct form for a hierarchical number.

When exporting or saving to a file that already exists, the user must give permission before the file is overwritten.

Database errors must be trapped and error messages displayed to the user. numeric value is expected.

Example: Field too long or a string entered when a

The minimum platform for the application will be a 386 PC running Windows with at least 8 MB of memory.

The on-line help must provide a point-of-contact for problems that are not solved by the on-line help.

The software shall provide a mechanism for identifying the current program and data versions.

The on-line help shall provide information on each non-trivial windows in the application.

The on-line help shall provide information about the underlying database structure.

The software shall provide a way for identifying the user making proposed changes to the baseline data by querying for and storing a user name during first time use.

10


5.0 OTHER CONSIDERATIONS

This section presents other considerations and requirements that are typically addressed separately in WHC-CM-3-10, Software Practices, Appendix F.

Functional Requirements: The functional requirements are covered in Section 4 above.

External Interface Requirements: There are no additional hardware, software, or communication interfaces for the Browser or Parser software.

Performance Requirements: Requirement 4, the software must run on a 386 PC running Windows with 8 MB of memory. denominator" for PCs onsite.

Design Constraints: None.

Attributes: None.

Other Requirements: documentation requirements are 1 isted in the Configuration Management Plan. Training will be addressed as needed. Other sections in Software Practices manual for defining potential requirements are not considered applicable.

As mentioned in Section 4.5,

This was chosen as the "lowest common

Testing and Acceptance criteria and

6.0 REFERENCES

WHC-CM-3-10, Software Practices, Revision 0, Appendix F, "Software

WHC-SD-WM-CSCM-034, TWRS Systems Engineering Software Configuration Management

Requirements Specifications, 'I Westinghouse Hanford Company.

Plan, Draft Revision, dated September 1996.

11

To From

D i s t r i b u t i o n Project Title/Work Order Requirements Management System Browser Software Requirements S p e c i f i c a t i o n

SE R i s k Management & Modeling

- RL

D. J . Franc is

Page 1 of 1 Date 9/26/96 EDTNo. 618218 ECN No.

- Other

Cent ra l F i l e s ( O r i g i n a l ) Log Book (D. 0. Frank)

Text Text Only Attach./ Name MSlN With All Appendix

Attach. Only

K6-51 X

EDT/ECN Only

A3-88 X H6-35 X

11-6000-135 (01/93) !&Fob7

twrs d. - digital library/67531/metadc685915/m2/1/high... · whc-sd-wm-sdr-011 rev. 0 1 .o...

Documents