Shrimad Rajchandra Institute of Management and Computer Application UTU
Shrimad Rajchandra Institute of Management and Computer Application UTU
Course Outcomes: Upon completion of the course, the student shall be able to
CO1: Comprehend the basic concepts and importance of traditional and object-oriented software
engineering.
CO2: Compare and contrast conventional and object-oriented software process models with its
applicability.
CO3: Recognize the prominence of V-model for development of quality software.
CO4: Identify needs and significance of requirements engineering using analysis modelling, data
and object-oriented modelling concepts.
CO5: Identify and design UML diagrams for a given system.
CO6: Classify and construct architectural, component level and user interface design for a given
system.
C07: Comprehend the latest software engineering development trends.
Programme Outcomes:
PO1: Proficiency in and ability to identify problems related to computer science as well as
design and apply computational knowledge to solve them.
PO2: Ability to design, develop, test and maintain system, component, product or process as per
needs and specification.
PO3: Understanding of professional and ethical role and responsibility.
PO4: Recognition of the need for and an ability towards life-long learning
PO5: Knowledge of programming languages, database systems, operating systems, software
engineering, Web & Mobile technology and relevant modern issues alongwith strong project
development skill.
PO6: Ability to demonstrate the use of modern tools, models and languages to solve problems
related to software development
PO7: An ability to communicate effectively with a range of audiences.
Programme Educational Objectives:
PEO1: To provide sound foundation in the fundamentals of computer application and
project development for life-long learning through quality education.
PEO2: To provide solid foundation knowledge to comprehend, analyze, design and test
computer applications and create problem solving attitude and research
aptitude.
PEO3: To provide technical skill of core as well as modern tools and technologies to
succeed in software industry profession as technocrat or become an
entrepreneur.
PEO4: To inculcate professional and ethical attitude along with teamwork, presentation
and communication to become leaders in service to industry and society.
Project Guidelines:
[B] Reporting
1. A student shall maintain a log book. Refer Annexure II for proposed logbook format.
2. A student doing project at institute so have to report about the project's progress to guide and
laboratory teacher during laboratory hours. Lab teacher need to maintain project progress and
take signature of students and also do signature of him/herself. Refer Annexure II for
laboratory work progress format.
[C] Evalution
1. To achieve quality and timeliness in project work continuous internal evaluation and
external evaluation scheme has been adopted.
2. There shall be two internal presentations of 30-45 minutes duration, which shall be
evaluated by examiner panel. During presentation, a student has to bring log book.
3. Student shall use presentation slides to explain the project work.
Objectives of Internal Presentations 1 and 2:
Parameter Marks
Requirement Gathering 15
with usage of subject
concept
UML diagrams 15
Presentation skills 10
Viva 10
Presentation 1 Outline:
Parameter Marks
Implementation of suggestion 5
given in Presentation 1
UML diagrams Data 20
Dictionary
Documentation 10
Presentation skill 10
Viva 5
Presentation 2 Outline:
Annexure I
Project Definition Report Submission
Project Title
General
functionalities
Distinct
functionalities
Technologies to
be used
Declaration:
We hereby declare that we have read the guidelines uploaded on website for the above said
course and we will follow those guidelines. We will not change the above given details for the
Date:
Place:
Annexure II
Annexure III
Report Format:
i. Title Page
ii. Project Certification Form [The certificate should be duly filled signed by internal
project guide and program coordinator.]
iii. Acknowledgement [All persons (e.g. guide technician, friends, and relatives) and
organization/authorities who/which have helped in the understanding of the project
shall be acknowledged.]
iv. Table of Contents with page numbering v. List of Tables, Figures, schemes
1. Introduction
1.1. Purpose
[Purpose means the objective to develop a project. Purpose describes what a project is
trying to achieve.]
1.2. Scope
[Project scope should have a good idea of what the project consists of (and what will not
be part of the project). This statement will give a view of the project.]
1.3. Definition, Acronyms, and Abbreviations
[An abbreviation/acronym is a shortened form of a word or phrase. Abbreviation
example: O.S. means Operating System Acronym example: GHz, which stands for
GigaHertz etc., which stands for et cetera Definition: a statement of the exact meaning of
a word]
1.4. Technologies to be used
[Mention the technologies i.e. hardware and software to be used in your project
development and required for deployment.]
2. System Analysis
2.1. Identification of Need
[Need describes the problem or issue, or situation where something needs to change to
make things better, for a person, a group of people, an environment or an organization.]
2.2. Functionalities
[This phase describes the functionality in system in following two parts:
• Usual functionalities.
• Distinct functionalities.
2.3. User Characteristics
[Identify classifications of users of your system. E.g. System administrator, client. And
write user wise functionality available in proposed system.]
2.4. Constraints and Assumptions
[Constraints and assumptions which the system must abide by during development.]
2.5. Software Development Process
[Models which used in system development.]
3. Conceptual Diagram
3.1. Use case diagram
[A use case diagram defines interactions between external actors and the system to attain
particular goals.]
3.2. Activity diagram
[Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency.]
3.3 Sequence Diagram
4. System Design
4.1. Data Dictionary, integrity constraints
Annexure IV
PROJECT
<<TITLE IN CAPITAL LETTERS>>
Submitted By,
<<Student’s Name (Enrollment Number)>>
<<Student’s Name (Enrollment Number)>>
Guided By,
<<Internal Guide Name>>