(C) 1997, DL, UTA

 CSE 5324			       Name___________________________________
 Software Engineering I
 Exam 1, Summer 1996


 Please read this:
 This is a closed book, closed notes exam. You may however use one note page
 of notebook size (letter) with hand written notes on one side. If you use a
 note page it must be turned in with this exam.
 Use a dark ink pen and print answers on the test paper following the question.
 Turn in all pages of the test. Write your answers legibly. Unreadable answers
 will be counted wrong. Make sure you have all pages of the test.
 Read each question carefully and be sure your answer addresses the question.
 If any question is unclear please raise your hand or come to the front of
 the class room. Please listen for any clarification given in class.
 This exam is a timed exam. You must complete the exam and turn it in
 before or at the end of class. No late exams will be accepted.
 Point values are given for each question. The exam has a total of 150 points.

 1. [90 pts]
   Short answers (maximum 50 words):
   a.) What are characteristics of "embeded" software?




       What are characteristics of "real-time" software?




  b.) The "classic" (or "waterfall") life-cycle model is a paradigm,
      modeled after the conventional engineering cycle, it is widely used.
      There are, however, 3 complaints or problems often encountered.
      Please list 2:
      1.



      2.



      Other than prototyping, please describe one other paradigm





  c.) Please list one advantage and one problem with prototyping:
      1.



      2.




  d.) How is project planning different from requirement analysis?




  e.) During the maintenance phase software defects are corrected. What are
      two other activities found in maintenance? (describe)
      1.)



      2.)



  f.) If a feasability study is warranted, list any 2 (of 4) primary areas
      of concern.
      1.)



      2.)




  g.) Balzer and Goldman propose principles of a good specification.
      One principle is: (1) that the system specification must be a
      cognitive model. Another (2) the specification must be operational.

      Please explain what one (1 OR 2) means and why this is important:





      [BONUS]
      Please explain what the other means and why this is important:





  h.) After the SRS is complete a specification review is conducted.
      Who should attend this review?


      What issues or questions are addressed, list 2:
      1.)




      2.)





2. [60 pts]
   The University of Software Engineering and Glass Blowing is automating
   student record keeping. To begin, they want to keep track of all
   students by name and student ID. They have all students currently
   enrolled fill out a card with name and student ID (or Soc Sec Num).
   This is entered into a large text file with each line containing a
   student name (2 to 4 "strings" of characters, each up to 12 characters,
   the last (name) is a maximum of 20 characters) followed by space(s)
   followed by the student ID (3 digits then "-", then 2 digits,
   then "-", then 4 digits.) While names may appear more than once
   (different students) student IDs may only appear once. Each part of a
   name must begin with a capital letter. Names must be all character.
   After reading the name list, invalid names, id's, duplicats, and errors
   will be reported. Then queries may be made on a terminal to look up
   if a name is on the list, or a student ID. If it is, all student info
   is displayed, otherwise a message is displayed.

   a.) Show a DFD (level 0).













   b.) Show a DFD (level 1) with 3 to 8 process "bubbles". (Don't forget
       any "control items" or "data store" if there are any.)































   c.) Show a requirements dictionary entry for a student ID.
       Use the content description notation discussed in class (and the text).
















   d.) Write a process specification (pspec) for a process that validates
       student names. Use a structured English specification style.