Software Project Management (November – 2018) [Choice Based | Question Paper]

Nov 11, 20191 like782 views

This document outlines the structure and questions for an exam on software project management. It contains 5 sections with 3 questions each, for a total of 15 questions. Students must answer 3 questions from each section for a total of 9 questions. The questions cover a range of topics in software project management, including project life cycles, project charters, portfolio management, estimation techniques, scheduling, risk management, configuration management, contract types, and project organization. The exam is 2.5 hours long and worth a total of 75 marks.

B.SC.IT: SEMESTER – V
[CBCS – Choice Based]
SOFTWARE
PROJECT
MANAGEMENT

SOFTWARE PROJECT MANAGEMENT
NOVEMBER – 2018 | CBCS – CHOICE BASED
MUMBAI UNIVERSITY
B.SC.IT: SEM-V
CHOICE BASED
| | | | | | | | | | 1 | Page
Time: 2 ½ Hours Total Marks: 75
NOTE:
(1) All questions (Q.1 to Q.5) are compulsory.
(2) Figures on the right indicate total marks. All sub-questions carry equal marks.
(3) Write the question numbers clearly as mentioned in the Question Paper.
(4) Mixing of sub-questions is not allowed.
(5) Draw diagrams and give examples whenever necessary.
(6) Use of calculator or any other electronic gadget is not allowed.
Q.1 ATTEMPT ANY THREE QUESTIONS: (15 MARKS)
(A) Briefly explain the different Phases of Project Management Life Cycle. (5)
(B) What is Project Charter in Software Project Management? What are the elements of Project Charter? (5)
(C) What is project Portfolio Management? Explain the key aspects of Project Portfolio Management. (5)
(D) Define the following terms:
i) Net profit
ii) Return on Investment
iii) Payback period
iv) Net present value
v) Internal rate of return
(5)
(E) What is a Project Product? Explain Product Breakdown Structure with the help of example. (5)
(F) What do you mean by scope and objective of a Project? List the activities involved in identifying project
scope and objective.
(5)
Q.2 ATTEMPT ANY THREE QUESTIONS: (15 MARKS)
(A) What do you understand by the term 'ceremonies' in a scrum project? Explain the different types of
ceremonies that are observed in a Scrum project and their significance.
(5)
(B) List the advantages and disadvantages of Software Prototyping. (5)
(C) Explain the five major components of Albrecht Function Point Analysis. (5)
(D) What is effort multipliers in COCOMO II model? List the Effort Multipliers used at Early Design. (5)
(E) Explain eight core principles of Dynamic Systems Development Method. (5)
(F) State Capers Jones rules of thumb for software estimation. (5)
Q.3 ATTEMPT ANY THREE QUESTIONS: (15 MARKS)
(A) With the help of example explain Forward Pass and Backward Pass to calculate activity duration in
Network Diagram.
(5)
(B) Define the following terms:
i) Critical Path
ii) Float
iii) Free Float
iv) Interfering Float
v) Hammock Activity
(5)

SOFTWARE PROJECT MANAGEMENT
NOVEMBER – 2018 | CBCS – CHOICE BASED
MUMBAI UNIVERSITY
B.SC.IT: SEM-V
CHOICE BASED
| | | | | | | | | | 2 | Page
(C) Explain Boehm’s Top Ten Software Project Risks and the different Strategies for reducing it. (5)
(D) Write short note on Project Evaluation and Review Technique. (5)
(E) Explain the different categories of Cost Incurred in a Software Project. (5)
(F) What is Resource Smoothing? Explain two different ways of prioritizing activities for resource allocation. (5)
Q.4 ATTEMPT ANY THREE QUESTIONS: (15 MARKS)
(A) Explain review Process Model with the help of diagram. (5)
(B) What is meant by Software Configuration Management? Explain the two principal activities of
Configuration Management.
(5)
(C) Explain the main sections in a requirement document for Contract Placement. (5)
(D) What is Fixed Price Contract? List the advantages and disadvantages of Fixed Price Contract. (5)
(E) What are three important categories of Stress Management Techniques? (5)
(F) Explain Vroom’s expectancy theory of Motivation. (5)
Q.5 ATTEMPT ANY THREE QUESTIONS: (15 MARKS)
(A) Explain the advantages of a Functional Organization Over Project Organization. (5)
(B) List the obstacles to Good Group Decision Making. Also explain Delphi Decision Making Process. (5)
(C) Write short note on SEI Capability Maturity Model. (5)
(D) What is Reliability Growth Model? Explain any two Reliability Growth Models. (5)
(E) What are the steps of conducting a post implementation Project Review? (5)
(F) Explain the different reason for which a Project may need to be terminated. (5)

The document discusses the main phases and models of the software development life cycle (SDLC). It describes common SDLC models like waterfall, spiral, and agile. The waterfall model involves sequential phases from requirements to maintenance. The spiral model is iterative with risk assessment. Agile emphasizes iterative development, collaboration, and responding to change. Testing methodologies like black box and white box testing are also summarized along with levels of testing from unit to system.

Waterfall model ppt finalshiva krishna

The document describes the waterfall model of software development. It begins by listing the presenters and defining sequential and incremental software development models. It then discusses the waterfall model in more detail, describing it as a linear sequential process where each phase must be completed before the next begins. The document outlines the history, use cases, diagram, phases and advantages/disadvantages of the waterfall model.

Internet Of Things (Question Paper) [October – 2018 | Choice Based Syllabus]Mumbai B.Sc.IT Study

This document is a question paper for the Internet of Things course from Mumbai University. It contains 5 questions with 3 subquestions each, for a total of 15 marks per question. Question 1 asks students to explain concepts like what IoT is, IP vs UDP protocols, and maintaining privacy of IoT devices. Question 2 covers topics such as prototyping IoT devices, open source technologies, and IDE features. Question 3 focuses on non-digital prototyping methods, APIs, 3D printing and CNC milling. Question 4 is about optimization techniques, types of memory, business models and funding IoT startups. Finally, Question 5 addresses PCB design, third-party manufacturing, crowdsourcing, certification and open

McCall's Quality FactorsUsman Khan

This document discusses software quality factors and McCall's model of quality factors. It describes McCall's model which categorizes quality factors into three categories: product operation factors related to how well the software runs, product revision factors related to how easily the software can be changed and tested, and product transition factors related to moving the software to different environments. Under each category it provides examples of specific quality factors like correctness, reliability, maintainability, and portability. It also mentions some alternative models that suggest additional quality factors.

Structural and functional testingHimanshu

This document discusses structural and functional testing. Structural testing generates test cases based on the internal structure of a program, while functional testing generates test cases based on the program's functionality without considering internal structure. Some types of structural testing include statement coverage, branch coverage, path coverage, and conditional coverage. Types of functional testing include equivalence class partitioning and boundary value analysis. Testing has limitations in that it can find errors but not prove their absence, does not help find root causes, and only identifies known issues without uncovered defects.

Software Engineering AssignmentSohaib Latif

The document discusses software process models for different project scenarios: 1. For building a larger, more complex application similar to previous projects where requirements are documented, the prototype model would be used to develop the application in increments and allow additions as needed. 2. For integrating departments within a university onto one system to accommodate all processes, the component model would be chosen to reuse existing components, modify requirements, and design the system to incorporate components while developing new software as needed to meet the timeline. 3. For developing the next version of word processing software with tight deadlines, the RAD (Rapid Application Development) model would be selected to allow parallel team work on components to meet the schedule. 4.

Software RequirementsNethan Shaik

The document outlines the software requirements engineering process, which includes gathering requirements from stakeholders, documenting them in a software requirements specification (SRS), and validating the requirements. It discusses the different types of requirements like functional, non-functional, and domain requirements. It also describes various techniques used for eliciting requirements, such as interviews, surveys, questionnaires, task analysis, domain analysis, brainstorming, and prototyping.

Spiral model of SDLCAnimesh Chakraborty

The document describes the spiral model of the software development life cycle (SDLC). It discusses the phases of the spiral model including planning, risk analysis, engineering, and evaluation. The spiral model is an iterative approach that combines elements of both design and prototyping-based development. It allows for incremental adjustments to requirements through repeated cycles. The model helps manage risk on large, complex projects that experience changing requirements over time.

Chapter13 designing forms and reportsDhani Ahmad

This chapter discusses the process of designing forms and reports. It outlines general guidelines for formatting forms and reports, including highlighting, color usage, displaying text, and designing tables and lists. It also covers assessing usability through factors like speed, accuracy and satisfaction. Specific guidelines are provided for designing interfaces for electronic commerce systems on the Internet, including using lightweight graphics, ensuring data integrity on forms, and implementing template-based HTML. The overall goal is to design forms and reports that are easy to use and understand.

Lect3 conventional vs modern spmmeena466141

This document compares principles of conventional and modern software management. It outlines 30 principles of conventional management including making quality a priority, giving products to customers early, and inspecting code. It then lists 10 principles of modern management such as using an iterative life-cycle process, establishing change management, and demonstrating intermediate artifacts. Finally, it discusses parameters for transitioning to an iterative process like prioritizing architecture, establishing process flexibility, and enabling team cohesion.

Graphical user-interfaceEstiak Khan

This document discusses graphical user interfaces (GUIs). It defines a GUI as a user interface that allows interaction through graphical icons, audio indicators, and pictures. The key features of a GUI include windows, icons, menus, and pointers. GUIs are easy to learn and use, allow quick switching between tasks, and replace multiple instructions with single icons. However, GUIs may consume more screen space and system resources and be slower than other interfaces.

Software security engineeringaizazhussain234

This document discusses software security engineering. It covers security concepts like assets, vulnerabilities and threats. It discusses why security engineering is important to protect systems from malicious attackers. The document outlines security risk management processes like preliminary risk assessment. It also discusses designing systems for security through architectural choices that provide protection and distributing assets. The document concludes by covering system survivability through building resistance, recognition and recovery capabilities into systems.

Hci unit 4( final)BekiTamirat

This document discusses human-computer interaction and interaction models. It provides objectives for describing elements of interaction models, identifying how ergonomics influences interaction, how interface styles influence dialog, and identifying interaction paradigms. Models of interaction discussed include Norman's execution-evaluation cycle and Abowd and Beale's framework. Translations between the user, input, system, and output are explained. Examples are given of how to apply these models to understand issues in interaction.

E voting UML diagramsmanasapeddalla

This document outlines the requirements for a small voting system module for student elections in a computer science department. It includes the names and IDs of three students on the project team, their batch and guide's name. Functional requirements include reducing manpower. Non-functional requirements specify minimum hardware specifications of 1GB hard disk, 2GB RAM, and a dual core processor. The scope is described as useful for department-wide voting only. It lists class, use case, activity, and sequence diagrams as parts of the system architecture.

Software Product LineHimanshu

This document defines a software product line as a set of software systems that share common features and core assets to satisfy the needs of a particular market segment. The goals of a product line are to reduce costs, improve delivery time, and improve quality through reuse. A product line consists of multiple related systems that share a common architecture and variability. It structures products through a core set of shared assets. The document discusses identifying and supporting variation points in a product line architecture and evaluating the architecture. It also covers adoption strategies, product line growth models, evolving a product line over time, and the benefits of reduced costs, improved time to market, higher quality, and more.

Requirement analysis and specificationM.E. at GTU- PG School

Chapter 15 software product metricsSHREEHARI WADAWADAGI

Online Voting System-using Advanced JavaSarthak Srivastava

This document proposes developing an online national polling system in India to address issues with the current in-person voting process. It would allow eligible citizens to vote online from anywhere by registering on the system's website. The system would use technologies like Java, MySQL database, and the Struts framework. It would have separate modules for voters and candidates, allowing voters to view candidate information, ask questions, and cast an online vote while candidates can register, update profiles, and respond to voter questions. The goals are to reduce time spent voting, enable global voting, and reduce voting errors.

Usability Engineering Presentation Slideswajahat Gul

extreme ProgrammingBilal Shah

Graphical User InterfaceDeepa Ram Suthar

Graphical user interfaces (GUIs) allow users to interact with electronic devices through graphical icons and visual indicators instead of commands. GUIs were created because command-line interfaces required users to spend a lot of time learning commands. Effective GUIs provide visual appeal through meaningful contrasts and groupings, are easily understood and learned through consistency and efficiency, and offer responsiveness by providing immediate acknowledgement of user actions.

requirement gatheringSaeedMat

Spiral model presentationSayedFarhan110

The document discusses the spiral model of software development. The spiral model is an iterative approach that combines prototyping and aspects of the waterfall model. It was defined by Barry Boehm in 1988 as a way to address risks through iterative evaluation and improvement of prototypes. The spiral model is best for medium to high risk projects where requirements are complex or expected to change. It involves evaluating prototypes, defining new prototypes based on learnings, and repeating this process until the final product is delivered.

Gathering requirementsDoan Truong Giang

This document discusses techniques for gathering software requirements, including interviews, workshops, observations, questionnaires, and document analysis. It outlines direct and indirect data collection methods, and levels of requirements from business goals to use cases. Stakeholder involvement at each level is described. The iterative nature of requirements elicitation and management is emphasized. Effective elicitation requires understanding stakeholders, crafting questions, and documenting open issues for future refinement.

Report on SOFTWARE DEVELOPMENT LIFE CYCLE SDLC Neetu Marwah

The document discusses the software development life cycle (SDLC). It describes SDLC as a process used in software engineering to break down development into distinct phases to better plan and manage projects. The phases include requirements study, design, development, testing, and maintenance. The document outlines each phase in detail and notes the key documents produced and activities involved at each stage of the SDLC process.

Software TestingMousmi Pawar

The document discusses various topics related to software testing including: 1. Software testing helps improve software quality by testing conformance to requirements and is important to uncover errors before delivery to customers. 2. Testing involves specialists at different stages from early development through delivery and includes unit testing of individual components, integration testing of combined components, and system testing of the full system. 3. Proper testing methods include black box testing of inputs/outputs, white box testing of code structures, and testing at different levels from units to full system as well as by independent third parties.

Software Engineering Past Papers (Short Questions)MuhammadTalha436

1. SWOT analysis is a framework for identifying internal and external factors that can impact a project, product, place or person. It analyzes strengths, weaknesses, opportunities, and threats. 2. Software refactoring is changing software code without altering external behavior to improve internal structure. 3. An embedded system is a programmed system within a larger mechanical or electrical system, often with real-time computing constraints and a dedicated function.

SDLC MODEL KOMAL DAHERIYA

The document discusses various software development life cycle (SDLC) models. It describes the phases of SDLC as requirements gathering and analysis, design, development, testing, implementation, and maintenance. Several common models are explained in detail, including the waterfall model, prototyping model, incremental model, and spiral model. The waterfall model follows a sequential process from requirements to maintenance, while other iterative models allow for more customer feedback and flexibility to change requirements over multiple iterations of development. Choosing the appropriate model depends on factors like project risks, requirements stability, and need for early delivery of basic functionality.

Project Management (December - 2018) [IDOL - Revised Course]Mumbai B.Sc.IT Study

Project Management (Question Paper) [May – 2018 | CBSGS - 75:25 Pattern]Mumbai B.Sc.IT Study

This document contains questions for an exam on project management. It asks students to answer questions in 2.5 hours with 75 total marks. Questions cover topics like Boehm's principles for staffing software projects, the three levels of processes and their attributes, parameters for estimating software project costs, symptoms of troubled projects, phases of the software development lifecycle, artifacts in management sets, software architecture, COCOMO II cost modeling, workflows in software development, work breakdown structures, roles and responsibilities in software organizations, quality indicators for software systems, metrics, process variability, comparing progress in modern vs conventional projects, cost modeling to support modern processes, culture shifts for modern processes, balancing principles for software economics, earned value analysis terms, and characteristics of

More Related Content

What's hot (20)

Chapter13 designing forms and reportsDhani Ahmad

Lect3 conventional vs modern spmmeena466141

Graphical user-interfaceEstiak Khan

Software security engineeringaizazhussain234

Hci unit 4( final)BekiTamirat

E voting UML diagramsmanasapeddalla

Software Product LineHimanshu

Requirement analysis and specificationM.E. at GTU- PG School

Chapter 15 software product metricsSHREEHARI WADAWADAGI

Online Voting System-using Advanced JavaSarthak Srivastava

Usability Engineering Presentation Slideswajahat Gul

extreme ProgrammingBilal Shah

Graphical User InterfaceDeepa Ram Suthar

requirement gatheringSaeedMat

Spiral model presentationSayedFarhan110

Gathering requirementsDoan Truong Giang

Report on SOFTWARE DEVELOPMENT LIFE CYCLE SDLC Neetu Marwah

Software TestingMousmi Pawar

Software Engineering Past Papers (Short Questions)MuhammadTalha436

SDLC MODEL KOMAL DAHERIYA

Chapter13 designing forms and reportsDhani Ahmad

Lect3 conventional vs modern spmmeena466141

Graphical user-interfaceEstiak Khan

Software security engineeringaizazhussain234

Hci unit 4( final)BekiTamirat

E voting UML diagramsmanasapeddalla

Software Product LineHimanshu

Requirement analysis and specificationM.E. at GTU- PG School

Chapter 15 software product metricsSHREEHARI WADAWADAGI

Online Voting System-using Advanced JavaSarthak Srivastava

Usability Engineering Presentation Slideswajahat Gul

extreme ProgrammingBilal Shah

Graphical User InterfaceDeepa Ram Suthar

requirement gatheringSaeedMat

Spiral model presentationSayedFarhan110

Gathering requirementsDoan Truong Giang

Report on SOFTWARE DEVELOPMENT LIFE CYCLE SDLC Neetu Marwah

Software TestingMousmi Pawar

Software Engineering Past Papers (Short Questions)MuhammadTalha436

SDLC MODEL KOMAL DAHERIYA

Similar to Software Project Management (November – 2018) [Choice Based | Question Paper] (20)

Project Management (December - 2018) [IDOL - Revised Course]Mumbai B.Sc.IT Study

Project Management (Question Paper) [May – 2018 | CBSGS - 75:25 Pattern]Mumbai B.Sc.IT Study

Project Management (April – 2015) [Question Paper | IDOL: Revised Course]Mumbai B.Sc.IT Study

Project Management (April – 2015) [Question Paper | IDOL: Revised Course] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Project Management (April – 2016) [Question Paper | CBSGS: 75:25 Pattern]Mumbai B.Sc.IT Study

Project Management (April – 2016) [Question Paper | CBSGS: 75:25 Pattern] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Project Management (October – 2016) [Question Paper | IDOL: Revised Course]Mumbai B.Sc.IT Study

Project Management (October – 2016) [Question Paper | IDOL: Revised Course] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Project Management (October – 2016) [Question Paper | CBSGS: 75:25 Pattern]Mumbai B.Sc.IT Study

Project Management (October – 2016) [Question Paper | CBSGS: 75:25 Pattern] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

B.Sc.IT: Semester - VI (October - 2017) [CBSGS - 75:25 Pattern | Question Paper]Mumbai B.Sc.IT Study

B.Sc.IT: Semester - VI (October - 2017) [CBSGS - 75:25 Pattern | Question Paper] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Project Management (October – 2014) [Question Paper | CBSGS: 60:40 Pattern]Mumbai B.Sc.IT Study

Project Management (October – 2014) [Question Paper | CBSGS: 60:40 Pattern] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Project Management (October – 2017) [Question Paper | CBSGS: 75:25 Pattern]Mumbai B.Sc.IT Study

Project Management (October – 2017) [Question Paper | CBSGS: 75:25 Pattern] april - 2017, april - 2016, april - 2015, april - 2014, april - 2013, october - 2017, october - 2016, october - 2015, october - 2014, may - 2016, may - 2017, december - 2017, 75:25 pattern, 60:40 pattern, revised course, old course, mumbai bscit study, mumbai university, bscit semester vi, bscit question paper, old question paper, previous year question paper, semester vi question paper, question paper, CBSGS, IDOL, kamal t, internet technology, digital signals and systems, data warehousing, ipr and cyber laws, project management, geographic information system

Pm941614119555Nikhil Todkar

This document contains a prelim question paper for a Project Management exam for TY B.Sc. (IT) students. The paper has 7 sections with 2 questions to attempt in each section. Section 1 asks students to answer questions about Boehm's principles of conventional software management, important trends in improving software economics, factors that can be abstracted with software economics, and comparisons of the three generations of software development. The document also provides the schedule for paper discussions to be held at various Vidyalankar centers between April 13-15, 2016.

BScIT: Semester – V (May - 2018) [IDOL: Old Course | Question Paper]Mumbai B.Sc.IT Study

BScIT: Semester – V (May - 2018) [IDOL: Old Course | Question Paper] ,2018 question papers ,may - 2018 questions paper ,bscit ,mumbai university ,mumbai university question paper ,revised course ,tybscit question papers ,bscit question paper ,semester 5 ,bscit semester 5 ,semester 5 question paper ,idol question paper ,idol revised course ,network security ,asp.net with c# ,software testing ,advanced java ,linux administration ,mumbai bscit study ,bscit study ,c# ,linux

B.Sc.IT: Semester – V (April – 2015) [Revised Course | Question Paper]Mumbai B.Sc.IT Study

Next Generation Technologies (November – 2018) [Choice Based | Question Paper]Mumbai B.Sc.IT Study

This document outlines the structure and questions for a B.Sc. IT semester 5 exam focusing on next generation technologies. It contains 5 sections with 3 questions each, covering topics like Big Data, NoSQL databases, MongoDB, jQuery, JSON, and more. Students must attempt 3 questions from each section. The exam is 2.5 hours long and carries a total of 75 marks. Diagrams and examples should be provided as needed. Use of calculators or other electronic devices is not permitted during the exam.

Object Oriented Programming (Question Paper) [April – 2017 | 75:25 Pattern]Mumbai B.Sc.IT Study

B.Sc.IT: Semester - V (October - 2013) [60:40 Pattern | Question Paper]Mumbai B.Sc.IT Study

B.Sc.IT: Semester – V (December – 2017) [Revised Course | Question Paper]Mumbai B.Sc.IT Study

This document contains a question paper for the Network Security subject for B.Sc. IT students at Mumbai University. It has 7 sections with a total of 100 marks. Each section contains 3-4 questions with varying marks. The questions cover topics related to network security such as Kerberos, IPsec, firewalls, viruses, worms, cryptography, digital signatures, public key infrastructure etc. Students are required to attempt 3 questions out of 4-6 questions in each section within the allotted time of 3 hours.

B.Sc.IT: Semester – V (October – 2012) [Revised Course | Question Paper]Mumbai B.Sc.IT Study

B.Sc.IT: Semester - V (April - 2014) [60:40 Pattern | Question Paper]Mumbai B.Sc.IT Study

[Question Paper] Advanced SQL (Revised Course) [April / 2014]Mumbai B.Sc.IT Study

B.Sc.IT: Semester – V (April - 2015) [75:25 Pattern | Question Paper]Mumbai B.Sc.IT Study