You are on page 1of 2

Midterm Examination Software Engineering

ITC 44 - 4031
CORTES,MBA,MPA,BSCS

Jose Rizal University

2nd Semester SY 2012-2013


Instructor: MELJUN P.

I.

Multiple Choice

(Select the best ans er amon! the !i"en choices# $%ITE &'() T*E (ETTE% on +our Test ,oo-let.

1.) It occurs when a component's algorithm or logic does not produce the proper output for a given input because something is wrong with the processing steps. a.) Algorit !ic "ault #.) Co!$utation an% $r&cision "aults c.) 'ocu!&ntation "aults %.) Ca$acit( or #oun%ar( "aults ).) Occurs when a formula's implementation is wrong or does not compute the result to the required degree of accuracy. a.) Algorit !ic "ault #.) Co!$utation an% $r&cision "aults c.) 'ocu!&ntation "aults %.) Ca$acit( or #oun%ar( "aults *.) Occurs when the documentation does not match what the program actually does. a.) Algorit !ic "ault #.) Co!$utation an% $r&cision "aults c.) 'ocu!&ntation "aults %.) Ca$acit( or #oun%ar( "aults +.) Occur when the system's performance becomes unacceptable as system activity reaches its specified limit. a.) Algorit !ic "ault #.) Co!$utation an% $r&cision "aults c.) 'ocu!&ntation "aults %.) Ca$acit( or #oun%ar( "aults ,.) Occur when a failure is encountered and the system does not behave as the designer desire or as the customer requires. a.) T roug $ut or $&r"or!anc& "aults #.) -ar%.ar& an% s(st&! so"t.ar& "aults c.) R&co/&r( "aults %.) Ca$acit( or #oun%ar( "aults 0.) Occur when the system does not perform at the speed prescribed by the requirements. a.) T roug $ut or $&r"or!anc& "aults #.) -ar%.ar& an% s(st&! so"t.ar& "aults c.) R&co/&r( "aults %.) Ca$acit( or #oun%ar( "aults 1.) Arise when the supplied hardware and system software does not actually work according to the documented operating conditions and procedures. a.) T roug $ut or $&r"or!anc& "aults #.) -ar%.ar& an% s(st&! so"t.ar& "aults c.) R&co/&r( "aults %.) Ca$acit( or #oun%ar( "aults 2.) 3erifies that the component functions properly with the types of input expected from studying the component's design. a.) Mo%ul&, co!$on&nt or unit t&sting #.) Int&gration t&sting c.) 4unction t&st %.) P&r"or!anc& t&st 5.) The process of verifying that the system components work together as described in the system and program design specifications a.) Mo%ul&, co!$on&nt or unit t&sting #.) Int&gration t&sting c.) 4unction t&st %.) P&r"or!anc& t&st 10. Evaluates the system to determine if the functions described by the requirements specification are actually performed by the integrated system. a.) Mo%ul&, co!$on&nt or unit t&sting #.) Int&gration t&sting c.) 4unction t&st %.) P&r"or!anc& t&st 11. !ompares the system with the remainder of these software and hardware requirements. a.) Mo%ul&, co!$on&nt or unit t&sting #.) Int&gration t&sting c.) 4unction t&st %.) P&r"or!anc& t&st 1 . "he system is checked against the customer's requirements description. a.) Acc&$tanc& t&st #.) Int&gration t&sting c.) 4unction t&st %.) P&r"or!anc& t&st 1!.) It make sure that the system still function as it should. a.) 4ault i%&nti"ication #.) Int&gration t&sting c.) Installation t&st %.) P&r"or!anc& t&st

6+.) The process of determining what fault or faults caused the failure. a.) 4ault i%&nti"ication #.) Int&gration t&sting c.) Installation t&st %.) P&r"or!anc& t&st
#E$JU% &. !'R"ES

6,.) "he process of making changes to the system so that faults are removed. a.) Acc&$tanc& t&st #.) 4ault corr&ction or r&!o/al c.) Installation t&st %.) P&r"or!anc& t&st

. .

II. Identi/ication ($%ITE &'() T*E (ETTE% on +our Test ,oo-let.


A. B. C. ". ). F. G. 1. +. 3. Prototype Process "e#eloper &estability ilestone +nteroperability +terati#e "e#elop%ent Critical Path etho! 2eliability "eli#erables K. L. . '. *. P. /. 2. S. &. Software Life Cycle U. Gantt Chart Flexibility V. Waterfall o!el Verification W. C$sto%er etho! (. Acti#ity +ncre%ental "e#elop%ent ,. Vali!ation User -. Software )n.ineerin. Pro0ect Sche!$le Syste% "e#elop%ent Life Cycle Synthesis 2e$sability

1.) "he items that customer expects and see during the pro#ect development. .) $nother term of software development process. !.) $ depiction of the pro#ect where the activities are shown in parallel% with the degree of completion indicated by a color or icon. &.) 'utting together of a large structure from small building blocks. (.) 'artially developed product that enables customers and developers to examine some aspect of the proposed system and decide if it is suitable or appropriate for the finished product. ).) "he system as specified in the requirement documents is partitioned into subsystems by functionality. *.) "he systematic approach to the development% operation% maintenance and retirement of software. +.) Is defined as a series of steps involving activities% constraints% and resources that produce an intended output of some kind. ,.) Includes simplicity% generality% modularity% software system independence and machine independence 1-.) Is the company% organi.ation or person who is building the software system for the customer. 11.) Is the completion of activity a particular point in time/ 1 .) Includes simplicity% instrumentation% self0descriptiveness and modularity 1!.) 1escribes the software development cycle for a particular pro#ect by enumerating the phases or stages of a pro#ect and breaking each into discrete tasks or activities to be done. 1&.) Is a part of the pro#ect that takes place over a period of time/ 1(.) Includes consistency% accuracy and error tolerance 1).) $ method which shows the minimum amount of time it will take to complete the pro#ect% given our estimates of each activity's duration. 1*.) 2nsures that each function works correctly. 1+.) Is the company% organi.ation% or person who is paying for the software system to be developed. 1,.) 1elivers a full system at the very beginning and then changes the functionality of each subsystem with each
new release.

-.) Includes expandability% generality and modularity.

III. Enumerate the 0esi!n 1uidelines in $ritin! 2ro!rams (0iscuss each !uidelines. - 13points

#E$JU% &. !'R"ES