web engineering workshop
DESCRIPTION
TRANSCRIPT
Web EngineeringA Discussion
D. J. Sanghvi College of Engineering7th August 2009.
Say what you feel!Are you confident of delivering the subject effectively?
Is the motivation behind introducing this subject clear to you?
Did you interpret the scope of the syllabus coverage correctly?
Were you involved in deciding the topics?
Do you believe that industry folks can be consulted for syllabus coverage?
StatisticsTotal Participants:10Aspects YES NO
Course Delivery Confidence? 7 3
Alignment with Motivation? 8 3
Scope Clarity? 1 8
Personally Involved? 3 6
Involve Industry Experts? 8 3
What still bothers us?What should we focus on: Software Engg. aspect or the Web Tech. aspect?
What should we cover for practical sessions: Software Engg. Aspect or Web Technologies?
What level of depth should these wide-ranging topics be dealt with?
How are we supposed to make students appreciate the architectures without students really knowing design principles?
Syllabus has implicit dependencies (pre-requisites) to design before we teach architectures
What still bothers us?What would students learn by visiting a software development center...this concept is good for other disciplines, but for software industry this idea of “Industry Visit” does not hold true
A Possible Approach for Term-work
Take a project based approach
Marry Software Engg and Web Technology aspects in a project-oriented approach for the entire semester (theory and practicals)
What you teach in class SHOULD be reinforced during practicals...one way out is to take a hand-in-hand approach for topics delivered in-class and topics done during practicals.
Choose a delivery approach, i.e Waterfall or any other SDLC or may be Agile
Slice the project or project modules based on chosen delivery approach and allocate slices to a group of students.
Chop the slice such that each sub-division becomes a term-work experiment spanning all the topics (to comply with university norms).
Evolve the slice in a natural progression where the first experiment is elaborated by the next and so on...until, the slice is ready for delivery.
A Possible Approach for Term-work
In short, iterate on the slice again and again and go on enriching it until deployment.
Make sure to test each sub-division of the slice.
Schedule and track each sub-division.
Term-work success criteria: a project that “RUNS” on “MY” machine.
Either you decide the project or let students come-up with project ideas, but you need to be consulted on the decision.
A Possible Approach for Term-work
ToolsAnalysis and Modeling
Eclipse Plugins
??
Design and Code
Eclipse, Netbeans or plain old notepad/vi.
JUnit, TestNG
Test
Unit Testing: JUnit, TestNG
Tracking
Wiki, OpenOffice, Excel, MPP
ParticipantsNarendra Sheokokar, D.J.S.C.O.E
Khushali Deulkar, D.J.S.C.O.E
Chetan Mahajan, P.V.P.P.C.O.E
Chitra Bhole, K.J.S.I.E.I.T, Sion
Hasmukh Sutar, Atharva College
Priyanka Desai, T.C.E.T
Bhagyashri Sonawale, S.C.O.E, Khargar
Asha Rawat, P.V.P.P.C.O.E.
Sheetal Pereiza, K.J.S.C.E, Vidyavihar
Gopal Gupta, T.S.E.C
Swati Ringe, F.R.C.R.C.E