swarnandhra 2018-19/iii_se.pdf3.1.4 requirements management t3,r2...

3
SWARNANDHRA College of Engineering & Technology (Autonomous) Seetharamapuram. NARSAPUR, W.G. Dt.,534 280. DEPARTMENT OF INFORMATION TECHNOTOGY LESSON PLAN SoFTWARE ENGTNEERTNG(R16) COURSE OUTCOMES: Students are able to CO1: Capabilities to identify, formulate, and solve software engineering problems. [K3] CO2: Elicit, analyze and specify software requirements with various stakeholders of a software development project. [K2, K4] CO3: Participate in design, clevelopment, deployment and maintenance of a medium scale software development project. IK3] CO4: Convey technical material through oral presentation and interaction with an audience. [K4] CO5: Evaluate the impact of potential solutions to software engineering problems in a global society, using the knowledge of models, tools, and tech les. Unit No Outcome Topics/Activitv Ref text book Total Periods Delivery Method t CO1: Capability to identify, formulate and solve engineering problems. [K3] *U.t)M".:l -l'.1-.!n!.r-o"-C-Hclip.n-tq-Sp.ft w-e"r.e.-Ensine--erine 1.1.1 The evolving role of software T1,R1 13 Chalk & Talk, Tutorial, Active Learning & Case Study 1.7.2 Software Characteristics T1,R1 1.1.3 Changing Nature of Software T1,R1 r.7.4 Software myths T1,R1 1"?.A_"G"en.--en-c_.yie,$,__.ol_"Prgge"s_-s L.2.7 software engineering- A layered technology T1,R1 7.2.2 A Process framework T1,R1 1,.2.3 The Capability Maturity Model lntegration(CMMI) T1,R1 7.2.4 Process assessment T1,R1 7.2.5 Product and Process T1,R1 2 CO2: Elicit, analyze & specify software requirements with various stakeholders of a software development. [K2, K4] u!!.!*!.1 2.1 Process models Chalk & Talk, Tutorial, Active Learning 2,L,L The waterfall model T2,R1 2.L.2 lncremental process models T2,R1 2.r.3 Evolutionary process models T2,R1 2.7.4 The Unified process T2,R1 15CS3T03 t INFORMATION TECHNOLOGY 5

Upload: others

Post on 28-Sep-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: SWARNANDHRA 2018-19/III_SE.pdf3.1.4 Requirements management T3,R2 3;..Preip-cl-p.Lq-n"ninc-en"C-es-t"imsl"i--o-n 3.2.7 Proiect Planning Activities T1,R2 3.2.2 Softv/are Metrics and

SWARNANDHRACollege of Engineering & Technology

(Autonomous)Seetharamapuram. NARSAPUR, W.G. Dt.,534 280.

DEPARTMENT OF INFORMATION TECHNOTOGY

LESSON PLAN

SoFTWARE ENGTNEERTNG(R16)

COURSE OUTCOMES: Students are able toCO1: Capabilities to identify, formulate, and solve software engineering problems. [K3]CO2: Elicit, analyze and specify software requirements with various stakeholders of a softwaredevelopment project. [K2, K4]CO3: Participate in design, clevelopment, deployment and maintenance of a medium scale softwaredevelopment project. IK3]CO4: Convey technical material through oral presentation and interaction with an audience. [K4]CO5: Evaluate the impact of potential solutions to software engineering problems in a global society,using the knowledge of models, tools, and tech les.Unit No Outcome Topics/Activitv Ref

textbook

TotalPeriods

DeliveryMethod

tCO1: Capability toidentify, formulateand solve engineeringproblems. [K3]

*U.t)M".:l

-l'.1-.!n!.r-o"-C-Hclip.n-tq-Sp.ft

w-e"r.e.-Ensine--erine1.1.1 The evolving role of software T1,R1

13

Chalk &

Talk,

Tutorial,Active

Learning& Case

Study

1.7.2 Software Characteristics T1,R11.1.3 Changing Nature of Software T1,R1r.7.4 Software myths T1,R1

1"?.A_"G"en.--en-c_.yie,$,__.ol_"Prgge"s_-s

L.2.7 software engineering- A layered technology T1,R17.2.2 A Process framework T1,R11,.2.3 The Capability Maturity Model

lntegration(CMMI)T1,R1

7.2.4 Process assessment T1,R17.2.5 Product and Process T1,R1

2

CO2: Elicit, analyze &specify softwarerequirements withvarious stakeholdersof a softwaredevelopment. [K2, K4]

u!!.!*!.12.1 Process models Chalk &

Talk,

Tutorial,Active

Learning

2,L,L The waterfall model T2,R12.L.2 lncremental process models T2,R12.r.3 Evolutionary process models T2,R12.7.4 The Unified process T2,R1

15CS3T03 t

INFORMATION

TECHNOLOGY5

Page 2: SWARNANDHRA 2018-19/III_SE.pdf3.1.4 Requirements management T3,R2 3;..Preip-cl-p.Lq-n"ninc-en"C-es-t"imsl"i--o-n 3.2.7 Proiect Planning Activities T1,R2 3.2.2 Softv/are Metrics and

2,2.5"-0,ftJr-are..Re_gsi.remenls2.2.7 User requirements T1,R1 132.2.2 System requirements T1,R12.2.3 Functional and non-functional requirements T1,R12.2.4 The Software Requirements Document (SRS) T1,R1

-ui!Lr_:[l3"'lB-e".qq-i.rsm--e.$s."Encin_e-F-rins.P_r_o-p-e-ss

3

CO3: Participate indesign, Development,Deployment &maintenance of a

medium scalesoftware developmentProject. [K3]

3.1.1 Feasibility studies T1,R2

74

chalk &

Talk,

Tutorial,Active

Learning& Case

Study

3.1.2 Requirements elicitation and analysis T1,R23.1.3 Requirements validation T1,R23.1.4 Requirements management T3,R2

3;..Preip-cl-p.Lq-n"ninc-en"C-es-t"imsl"i--o-n3.2.7 Proiect Planning Activities T1,R23.2.2 Softv/are Metrics and Measurements T1,R23.2.3 Software Metrics and Measurements T1,R23.2.4 Eff ort Estimation Techniques:

COCOMO, PERT/CPM method.T1,R2

Mrp tExAMtNATtqN4 CO4: Convey technical

material through oralpresentation andinteraction with anaudience. IK4l

UNIT.IV4.1 Desien Enpineerine

Chalk &Talk,

Tutorial,Active

Learning& Case

Study

4.1.1 Design process and Design quality T1,R2

13

4.L.2 Design concepts T1,R24.1.3 Software Architecture T1,R24.1,.4 Architectural Styles and Patterns T1,R2

--

{,?"9bje--cj.:9.rie"n"ted..-D_e__cign4.2.7 Obiects and obiect classes T1,R24.2.2 An Object-Oriented design process T1,R24.2.3 Design evolution T1,R2

5

CO4: Convey technicalmaterial through oralpresentation andinteraction with anaudience. [K4]

-u".lll-r-:Y5"1_.P-er.f.erming..U_s_e_r-!.nl9r"f.e-c.-e_..p".es!cn

13

Chalk &Talk,

Tutorial,Active

Learning& Case

Study

5.1. L Golden Rules T2,R25.1,.2 User interface analysis and design 't2,R25.1.3 lnterface design steps T2,R25.1.4 Design evaluation 12,R2

5?_r"ee!ina"s-Lr_a!ecie_r.5.2.7 A strategic approach to software testing T2,R25.2.2 test strategies for conventional software T2,R25.2.3 Validation testing T2,R25.2.4 System is testing T2,R25.2.5 the art of Debutging r2,R25.2.6 Black-Box and White-Box testing T2,R2

Page 3: SWARNANDHRA 2018-19/III_SE.pdf3.1.4 Requirements management T3,R2 3;..Preip-cl-p.Lq-n"ninc-en"C-es-t"imsl"i--o-n 3.2.7 Proiect Planning Activities T1,R2 3.2.2 Softv/are Metrics and

6COS: Evaluate theimpact of potentialsolutions to softwareengineering problemsin a global society,using the knowledgeof models, tools, andtechniques. IK4]

UNII;VlEt.B!s.k,men"aseme-nt

6.1.1 Reactive vs Proactive risk strategies TZ,R2

T4

Chalk &Ta lk,

Tutorial,Active

Learning& Case

Study

6.L.2 Software risks T2,R26.1.3 RMMM T2,R26.r.4 RMMM Plan T2,RZ

9r...?.Rq-eli!y..Menacsment6.2.L quality concepts T2,R26.2.2 Software quality assurance 12,R26.2.3 Software Reviews T2,R76.2.4 Formal technical reviews T2,R26.2.5 Statistical Software quality Assurance '12,R2

6.2.6 Software reliability T2,R26.2.7 The ISO 9000 quality standards '12,R2

5.2.8 Metrics for software quality 12,R2

TOTAT 80

MID IIEXAMINATION

END EXAMINATION

TEXT BOOKS:

T1: Software Engineering, A practitioner's Approach- Roger S. pressman, 6th edition, McGraw-Hilllnternational Edition,

T2: Software Engineering- Somerville, 9th edition, Pearson education.

REFERENCE BOOKS:

R1: Software Engineering- K.K. Agarwal & Yogesh Singh, New Age lnternational publishers

R2: software Engineering, an Engineering approach- James F. peters, witold pedrycz, John wiely.R3: Systems Analysis and Design- Shely Cash man Rosenblatt, Thomson publications.

R4: Software Engineering principles and practice- Waman S Jawadekar, The McGraw-HillCompanies.

h.\-{.PRINCIPAL

Qtteml"trlr"FACULTY