Project 1<o:p></o:p>

Data Structures (CNCE201)<o:p></o:p>

Fall 2010<o:p></o:p>

Project Deion<o:p></o:p>

<o:p> </o:p>

In thisproject, you will develop a simple information management system to be used byan organization in managing program activity information of its members participatingin a certain program. The activity information is arranged for everyparticipating member, all sorted by the participant’s employee id as the key. Eachparticipant’s activity information comprised a set of information pieces as pictoriallyshown below:

The activityinformation details, as pictorially shown below, enlist the detailedinformation on every activity in which the member participates.

The program,starting with no data put in the system, first creates an empty linked list ofactivity participants, then iterate at the top level of reading and processingcommands for activity information management. The system will handle thefollowing commands:

dump_all_participants<o:p></o:p>

add_Actinfo<o:p></o:p>

delete_Actinfo<o:p></o:p>

change_Actinfo<o:p></o:p>

show_participant_info<o:p></o:p>

end<o:p></o:p>

<o:p> </o:p>

Thesyntax of the commands will be shown by a set of sample commands to be providedlater.  

<o:p> </o:p>

Work to be submitted<o:p></o:p>

Thefollowing files, all zipped together in one zip file, should be submitted dueby 24:00 p.m. of Monday November 15:

1)      source code file: <u>xxxxxxxx</u>dman.c

2)      executable file: <u>xxxxxxxx</u>dman.exe

3)      output file: <u>xxxxxxxx</u>out.<u>yyy</u>

4)      project note: <u>xxxxxxxx</u>PN<u>.yyy</u>  (this file is optional and will not be graded)

where

   <u>xxxxxxx </u>stands for the last 7 digitsof your student ID and

   <u>yyy</u> stands for appropriateapplication file extension widely recognized on MS Windows platform.

Project 1<o:p></o:p>

Data Structures (CNCE201)<o:p></o:p>

Fall 2010<o:p></o:p>

Input data specification<o:p></o:p>

<o:p> </o:p>

Theinput that the program you will build for Project 1 will accept will meet thefollowing specifications:

1.      The system will read in asequence of user commands from a file named as “dman.txt” stored in thedirectory where the executable program is located;

2.      Each command will be delimitedby a pair of brackets ([ and ]);

3.      Each user command will beidentified in the input by a command code as defined below:

4.      Gender information will becoded by the gender code as defined below:

<o:p> </o:p>

5.      Each information field in acommand will be led by a field identifier as defined below and followed by anequal sign (=);

6.      The end of each informationfield is delimited by at least one white space except for the last one, whichmay or may not be delimited by white spaces.

7.      For a member whose data is tobe newly added in the database, the command must provide all the informationfields;

8.      For a member whose data isalready in the database, the command may not contain the information fieldsthat remain unchanged except for the key fields (Eid and Actinfo);

9.      As of now, there are 10activities handled by the system which are identified by the activity codes asdefined below:

<o:p> </o:p>

<o:p> </o:p>

Anexample given below shows a possible command sequence:

<o:p> </o:p>

[ 11eid=U431 ln=Brown fn=Ted gen=1 aid=103 jd=20080413 lv=0 ]

[ 11eid=M26 ln=Utkoff fn=Mary gen=2 aid=104 jd=20091003 lv=0 ]

[ 11eid=U257 ln=Doe fn=John gen=1 aid=114 jd=20091103 lv=0 ]

[ 11eid=M26 aid=116 jd=20100110 lv=0 ]

[ 10 ]

[ 13eid=M26 aid=104 lv=1 ]

[ 14eid=M26 ]

[ 11eid=U257 aid=116 jd=20100113 lv=1 ]

[ 12eid=U257 aid=114 ]

[ 12 eid=U431aid=103 ]

[ 10 ]

[ 15 ]

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> </o:p>

<o:p> 이거 프로젝트 원문 ㅇㅇ</o:p>