My Profile
Active Members
TodayLast 7 Days
more...
Awards & Gifts
Online Exams
Fresher Jobs
Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian
cities including Bangalore, Chennai, Hyderabad, Pune or Kochi
Resources
Find educational articles, blogs, discussion threads and other resources.
Colleges
Find details about any college in India or search for courses.
|
Syllabus of Andhra University MCA - MCA 3.1.6 Object Oriented Software Engineering Lab
Posted Date: 16 Feb 2008 Resource Type: Articles/Knowledge Sharing Category: General
|
Posted By: rajasekhar Member Level: Gold
Rating:  Points: 4
|
|
|
Syllabus of Andhra University MCA - MCA 3.1.6 Object Oriented Software Engineering Lab
With effect from 2004-05 admitted batch
Instruction: 3 Periods/week
Sessional Marks: 50
Univ-Exam-Marks:100
Time: 3 Hours
The purpose of the Software Engineering Lab course is to familiarize the students with modern software engineering methods and tools, Rational Products. The course is realized as a project-like assignment that can, in principle, by a team of three/four students working full time. Typically the assignments have been completed during the semester requiring approximately 80-120 hours from each project team.
The goal of the Software Engineering Project is to have a walk through from the requirements, design to implementing and testing. An emphasis is put on proper documentation. Extensive hardware expertise is not necessary, so proportionate attention can be given to the design methodology.
Despite its apparent simplicity, the problem allows plenty of alternative solutions and should be a motivating and educating exercise. Demonstration of a properly functioning system and sufficient documentation is proof of a completed assignment
Projects
Term projects are projects that a group student or might take through from initial specification to implementation.
The project deliverables include:
* Documentation including
o A problem statement
o A requirements document
+ A Requirements Analysis Document.
+ A System Requirements Specification.
+ A Software Requirements Specification.
* A design document
o A Software Design Description and a System Design Document.
* A test specification.
* Manuals/guides for
o Users and associated help frames
o Programmers
o Administrators (installation instructions)
* A project plan and schedule setting out milestones, resource usage and estimated costs.
* A quality plan setting out quality assurance procedures
* An implementation.
References
1. Project-based software engineering: An Object-oriented approach, Evelyn Stiller, Cathie LeBlanc, Pearson Education
2. Visual Modelling with Rational Rose 2002 and UML, Terry Quatrini, Pearson Edusction
3. UML2 Toolkit, Hans-Erik Eriksson, etc; Wiley
|
Responses
|
No responses found. Be the first to respond and make money from revenue sharing program.
|
|
Watch TV Channels
|