Project background 

Internet security is the primary research area these days and as the usage of the internet applications is increased drastically the threats caused across the internet are also increased a lot. There are different types of threats to the internet security and the corresponding solutions are given against these threats. Even there are many possible ways to reduce the internet security threats; there is always a scope to introduce the risks in the form of threats to the internet security and in general these threats can be from different sources like virus, Trojan horse and worms. Among these types of attacks, worms have a significant effect on the internet security and there are different types of worms that affect the security of internet.

In general a worm is similar to that of a virus and they replicate themselves and occupy the primary memory and does not affect the system files as a typical virus operation do and they simply reduces the system resources and thus the overall performance of the system is effected a lot. Active worms are heavily detected these days and in general these active worms propagate in to the internet in the form of a malicious software program and effects the other computers that were connected to the internet. There are different types of worms that has affected the internet security in future and few of them include Slammer, Code-Red and Witty and these worms has created a lot of security threats across the internet and following are the important security threats created by these worms 

• Distributed Daniel of service attacks (DDOS) are launched across the internet and the key internet utilities are corrupted
• Confidential information is accessed and the corresponding damage is created to the internet resources
• Distribution of malicious programs in the form of spam emails and messages 

Due to these attacks on the internet, there is lot of work against the worm detection and deletion methods and irrespective of these efforts, always there is a scope of new worm that are emerging on the internet and one among them is Camouflaging worm (C-worm). This type of worm is similar to a traditional worm, where they replicates and affects the system resources and they can affect all the computers connected to the internet at the same time. The actual aim and objectives of this research are as given below 

Aim: To develop a modeling technique to detect the camouflaging worms and evaluates the methodologies to protect the internet security. 

Objectives 

Following are the research objectives 

• To critically review different types of internet security threats and analyze their effect on the internet security
• To analyze different types of internet security threats created by worms and review the various detection systems and their limitations
• To design a modeling and detection system to detect the camouflaging worms using Java as the programming language
• To code the proposed system using Java
• To evaluate the results against the aim of the project and conclude the overall system performance with the implication of the proposed system. 

How these objectives will be achieved 

1. To critically review the types of internet security threats, different sources like online articles, journals, publications and ACM library are referred to gather the required information to do the literature review
2. Literature review holds different aspects like review on internet security, different types of security threats like virus and worms and their corresponding affect on the internet security
3. Different resources as mentioned across point 1, are used to gather the information related to different types of worms and various detection techniques are reviewed and their limitations are also evaluated
4. Design of the proposed system  is done and this design holds the following aspects 

• Front end design of the application
• User interactions to the application
• A module to insert the camouflaging worms to the existing internet applications
• A detection module to detect the worms
• Database design

1. Coding is done using the java programming language and the corresponding database tables are created using SQL database and following aspects are covered under the coding
   1. Front screens coding
   2. Business logic coding
   3. Database coding
   4. camouflaging worms coding
   5. Detection module coding
   6. Results are evaluated against the proposed system and the performance of the detection module is tested.

Implementation procedure 

A java based web application is created that can be used for online education and different roles are created with respect to the application like administrator and student. Following modules are created with respect to this application 

Administrator: Administrator has all the rights on the application like verifying the student details, registering them, registering the teachers, adding the course details and question papers 

Students: Students can login or register to the system and view the course details and write the online examinations. 

Worm module: A separate worm module is created across the application and this  module when initiated, duplicates the files in the database and deletes some important content from the database like the questions papers, course details and also duplicates the number of students such that the administrators when trying to access the student reports gets confused and also the available space across the database is occupied by the duplicate files. 

Detection module: Detection module when initiated by the administrator can detect the affected files from the database and a log file is generated with respect to the worm affected files with the corresponding extensions and thus the administrator can delete them. 

Reasons to choose this project 

In general there are different types of interne security threats faced these days and irrespective of the number of efforts given towards the detection of worms and virus, always there is scope of newly introduced worms every day. I am interested in the internet security area and chosen this topic and will implement a camouflaging worm detection mechanism to ensure the internet security. 

Resources 

Following are the hardware and software requirements for this project 

Hardware Requirements: 

PROCESSOR        :    PENTIUM IV 2.6 GHz

RAM                    : 512 MB 

Software Requirements:

Operating System: Windows XP

 Tools required: JDK 6.0

Database: Oracle 10 G  

Project plan  

Task	Description	Start Date	End Date	Duration
Introduction	Basic introduction to the project along with the problem definition and aims and objectives are defined in this section.			1 week
Literature review	Following topics are covered under literature review  Review on different internet security threats like virus and worm Review on different types of worms and the corresponding detection techniques Review on limitations of the existing detection techniques			4 weeks
Design	Following design aspects are covered under this section   Front end design of the application Database design Modules design			3 weeks
Coding and Implementation	Following aspects are covered under the implementation section  Coding all the modules Establishing the database connections Implementing the modules Explanation to the important coding functions			4 weeks
Evaluation of results	Results achieved after running the individual scenarios and after comparing the scenarios are explained in this chapter with reference to the aims and objectives of this project.			2 weeks
Conclusion and Future work	Conclusion from the total work done and the results evaluation is given and the better ways to improve the project in future are also explained.			1 week

 

 

Deliverables

 

Following are the project deliverables 

Initial report contain the following information 

• Review on different types of virus and worms and their affect on the internet security
• Review on different types of worms and the corresponding detection techniques 

Interim report contain the following information 

• Design of the application covering the front end and database design
• Implementation procedure and explanation to the coding logic followed 

Final report contain the following information 

• Information from both the initial and interim report
• Literature review
• Design
• Coding and implementation procedure
• Evaluation of results
• Conclusion and future work 

Final product contains the following information 

• Rich user interface with an internet application
• Worm detection module
• Database

• MSc Project Title 
• Should the same as the approved title 
• Name:
• Student ID:
• Programme of Study:  
• Date Proposal Submitted:  
• Project Hand In Date: 
• Supervisor:

Part A – Progress Report 

This follows the same format at the initial report and has the same 3 sections.  It should be 500-1,000 words in length. 

1. Current Situation

This section should include scheduled objectives and sub-objectives and whether they have been achieved.  If not fully achieved then explain why, and give details of those in the process of being achieved, preliminary results, work completed, etc.

1. 2.      Problem areas

This should cover current problems and plans for their resolution.

1. 3.      Key work during the next period

Specify methods, tasks and activities and the estimates of time to complete them. Indicate the actual progress made and identify any deviation from the original proposal and plan. 

Part B – Project Report to Date 

This should be a minimum of 2,000 words and must include: 

1. Table of Contents for your final report, with annotations concerning your intentions for the chapters.  It is recommended that you use the Table of Contents feature of Word for this. 

1. Draft of at least two chapters – one of which must be the literature review. 

1. Comprehensive Bibliography of all the work you have consulted. 

Your supervisor will give you feedback on your progress at this stage and will make recommendations for the final stage of the project.

The Initial Report

(1,000-1,500 words) 

The aim of this report is to inform the supervisor of the current project status and to review the feasibility of the project and objectives.  It is important that this procedure concentrates on the key issues and that it requires the minimum of effort on the student’s part. The report should give a summary of the overall project status.  It should include a header page and three sections: current situation, problem areas and key work during the next period. 

Current situation

In this section, describe the completed work.  This should include an account of the literature survey to date – what books and articles have been consulted and how the material fits in with what one is planning to do. This should be supported by a Bibliography in Harvard Reference format (or equivalent) as described in the project lectures and on the projects pages of the CMS Student Intranet. 

Problem Areas

The problem areas should describe the critical factors that will affect the meeting of target dates. Now is the time to bring to your supervisor’s attention any problems that have arisen so far.  This includes problems in obtaining equipment and software – and access to key people. This acts as an early warning system and focuses attention on the matters requiring urgent attention. 

If it is found that the project scope was too ambitious and some aspect of it needs to be revised then there is still time to make changes so you have a chance of completing on time. Any changes will need to be approved by your project supervisor. 

Key work during the next period

In this section specify methods, tasks and activities plus the estimates of time to complete them. Indicate the actual progress and identify any deviation from the original proposal and plan.  

The Initial Report should be uploaded via the link on the project pages on the CMS Student Intranet.

Variable thickness has a wide role to play in the field of computer graphics and designing many mechanical objects. There are many wide ranges of applications that basically run on the principle of variable thickness and most of these applications run on the formula of two dimensional coordinate space. A two dimensional coordinate space can be defined as the space that is represented by two points geometrically and the thickness and surface area of any object can be defined in the terms of these two points.

Different applications related to physics, computer graphics and engineering subjects has implications over the surface related issues in terms of both the longitude and latitude aspects of the coordinate space. A simple example for this case is aerodynamics, where the airplane central properties are mainly dependent on the variable thickness and surface dynamics. Animation and interface design fields also include their place across the variable thickness and surface aspects. Main aim of this project is to critically review importance of variable thickness surfaces and its applications in different areas with respect to few examples.

Technical aspects of the surface designed are reviewed and a research analysis section is covered to understand the in depth implementation and design aspects of coordinate system of Variable thickness space. Applications and technical implementations of variable thickness surface across the computer graphics filed is studied in this project with detailed analysis of the design aspects. MATLAB simulation is used to calculate the thickness of a surface using the algorithm to generated shape of the surface mesh using a finite element method (FEM). A mathematical approach is used to determine the 3D surface from a 2D surface using a free-form surface generation. 

Surface 

The term surface can be defined as the outer boundary of an object or artifact. Surface can be used to estimate the geometrical attributes of an object and in general there are different definitions that define the surface in different perspectives. If a three dimensional object is considered, a surface can be defined as the extended two dimensional outer boundary of the corresponding object. In general a surface can be explained as the boundary between an object and non object and can be considered as the limit for a visual perception.

A surface of an object is the boundary that can be represented in the form of three dimensional aspects in the Euclidean space R³ and the best example for this case is the surface of a ball or cube. Even there are some cases, where the surfaces can’t be represented as the three dimensional manner and the best example that can be considered related to this case is the Klein bottle, where the surface of this bottle cant be embedded in the three dimensional Euclidean space and a 3D approach can be achieved with the implementation of self interaction points across the boundaries. There are different applications that run with the perfect implementation of this surface concept and these include physics, computer graphics, mechanical engineering and other engineering areas.

The historical definition of surfaces defines surface as a subspace of Euclidean spaces. Surface can be stated as the topological space that holds certain properties like every point across this space has a non empty neighbor homeomorphic to an open subset of Euclidean plane E^2. In general surfaces can be of two types like closed surfaces and non-closed surfaces. A closed surface is compact in nature and has no boundary and a non-closed surface always holds a boundary and the example that can be considered here is a punctured cube.

The complete visual perception of an object can be estimated with the surface characteristics of that particular object and this is the main reason why there is lot of scope across the study of surfaces in computer graphics. In the field of computer graphics the surface of an object is represented as rigid and explicit triangular meshes. Thickness of a surface plays a very important role in identifying the physical characteristics of an object and in general this thickness can be either constant or variable. Variable thickness surface of objects has a wide range of applications and lot of scope to research. Deriving the variable thickness surfaces has wide scope to study across the fields like computer graphics and aerodynamics.

Variable thickness surfaces include objects like curves and rigid surface objects. Even bending surfaces can be considered as an example of variable thickness surfaces and there are several forces that act on the bending surfaces and make the thickness attribute as variable. Surface tracking of variable thickness surfaces can be considered as an important problem across the research and computer graphics is the best example of this case. In general in the field of computer graphics, variable thickness surface and rigid surface objects are represented as triangular meshes. 

Curved Surfaces 

Curved surface are in general of variable thickness and can be represented in several forms. A good curve surface representation should include few important aspects as discussed below 

Accuracy: The curved surface should be represented in a manner such that the required dimensions and attributes can be measured accurately. Parameters to measure the variable thickness of the surfaces should be focused more in the process of representation. 

Concise: Representation of the curved surface should be as simple as possible and the complex functions and algorithm should be avoided in the process of curved surfaces. In general this curved surface has variable thickness and to measure and represent these aspects, the mathematical functions should be as simple as possible 

Affine Invariance: Curve representation should follow basic principle of geometry like Affine Invariance and a curve is said to be affine invariance if the relative coordinate system is changed without affecting the geometry of the curve. Variable thickness can be identified with the coordinates of the curve and if the required curve is affine invariant, representation and identification this thickness would be much easier.    

Arbitrary Topology: Topology should be flexible enough while representing the curved surfaces. There should not be any standard functions and rules while representing the required curved surfaces and the thickness of these surfaces will vary across the curve and thus a perfect arbitrary topology should be implemented across the representation of the curved surfaces. 

Introduction

Software development has taken many forms these days and always new and sophisticated techniques are introduced with respect to software development process. Initially development of software is considered as the biggest task as it includes many steps and procedures to complete a single cycle of software development . There are many software development models proposed across the literature of software engineering and each of them are proved to be successful in few aspects and failed to contribute the maximum level of development feasibility with respect to the software development process.

Across any software development methodology, the crucial step that should be given the top priority is the requirements gathering phase and the software vendors almost spend 30 to 40 percent of the software development time in gathering the requirements . Requirements gathering are the key step across the software development process and there are different techniques followed by the software organizations with respect to this step and apart from the level of efforts buried across the requirements gathering phase, at some time the clients or the vendors fail to contribute their best in delivering the requirements. The traditional way of gathering the requirements for a particular software development includes many meetings among the clients and software vendors and they use to come to a common agreement with respect to the requirements.

Whenever the requirements are freeze, modifications to the client requirements and changes to the current work done is done in most of the cases, due to miscommunication at the stage of meetings done at the requirements gathering stage and due to lot of rework is done and finally the project deliverables are affected a lot with respect to this. Due to miscommunication and less interaction at the requirements gathering phase, there are some cases where the project are failed abruptly and the clients and vendors end up with lot issues. In general a requirements gathering phase include lot of hidden issues and the clients and vendors should be wide open enough while explaining the requirements and each and every step that should be included in the software should be discussed in detail, such that changes in the requirements and modifications to the software developed will be reduced in future.

Irrespective of the efforts kept by the clients and vendors at the requirements gathering phase, always there would be lot of issues that can’t be avoided and thus to reduce these issues, there are many tools that were in the implementation for a perfect requirements gathering methods. Requirements gathering has very important role in software development and even there is a separate area with respect to this like requirements engineering where different methodologies and frameworks are introduced with respect to requirements gathering phase and different requirements gathering techniques are introduced with respect this phase.

In general requirements can be categorized in to different types like client requirements, architectural requirements, functional requirements, structural requirements, behavioral requirements, design requirements and performance requirements. If the clients and vendors are not clear with any of these requirements the software that is being developed would end up with lot of issues irrespective of the number of tools and techniques followed in gathering the requirements in the software development process.

Waterfall project management is a well know technique followed across many projects and proved to a successful implementation with respect to the requirements gathering phase and later where the client requirements are changing and increasing this model could not handle the changes in an effective manner, as the waterfall project management model is sequential and there is no scope to handle the changes as back tracking the model is not possible with respect to this model. To solve these issues, always there is lot of research done with respect to a perfect implementation of a tool that can handle the software development and requirements and the recent development in this area is Agile project management model.

Agile project management is an iterative model, where handling the changes in the requirements can be done effectively as there is scope for lot of iterations. Requirements are determined from the client in an iterative manner and even the software can be delivered in a highly effective and interactive manner. In general Agile project management has many implementations for a perfect requirements gathering step and delivery of the project and the main of this project is to investigate and critically review the importance of Agile in project management and different tools involved in the Agile framework . 

Agile scrum methodology is commonly used methodology used these days across the software development process. The main advantage with the Agile scrum methodology is that is follows an empirical process control framework across the software development process. In general the agile scrum methodology uses the accurate and real time progress of the data rather than the assumptions or best guess process across the software development process. Agile scrum methodology is applied to the software development process in parts and these parts are usually known as sprints and these sprints are something like the deadlines.

In general these sprints can be of one week, two weeks or three weeks and so on and at the end of each sprints, the project stakeholders and the team members review the progress done across each sprint and if the required aspects are covered across the sprint, then the sprint is said to be successful or it is declared as sprint fail, even a small deliverable or update is missing across the sprint. In general there are different roles across the Agile scrum methodology like the Product owner, Scrum master and team member and each of these roles as some responsibilities to be executed. 

Following are the research questions identified with respect to this research 

• What is the importance of Agile project management and how it is different from existing project management models?
• What are the different Agile project management methodologies and what is their role against different phases of software development?

Aims and Objectives 

Aim: To investigate and critically review the importance of Agile project management with respect to various stages of software development

Objectives 

Following are the research objectives 

• To review different software development models and evaluates the key limitations in comparison to Agile project management method.
• To critically evaluate different Agile methodologies with respect all the stages in the software development process
• To understand the Agile life cycle and different tools related to Agile project management method.
• To review the concepts like scaling the Agile, Agile design and Agile testing and evaluate the corresponding implementation procedure. 

Literature review

Agile project management is widely used across many organizations these days due to the number of excellent features available with Agile framework. The key feature available with Agile frame work is that it provides a very light weight components across the software development method and also light weight activities that can be used for a simple way to project development and deployment. In general these activities include all the required components at each stage of software development like requirements gathering, design, coding and testing the software.

Most of the agile development methodologies concentrate on the software management aspects, but the key functionality of agile framework is enhanced at the stages of coding, testing and delivery of software artifacts. In general as per the definition of software engineering institute, a project management methodology should meet some basic requirements and methods to be called as a perfect methodology and a typical project management model should include some key features as listed below 

• Quality
• Product
• Standards
• Activities
• Techniques
• Milestones
• Team
• Work environment
• Skills
• Roles
• Project management tools
• People

All the key features included above should be perfectly connected and collaborated to achieve a perfect project management model and in general Agile is completely built on this basis and holds the complete grip on every aspect as listed above. The main focus of this type of framework is concentrated on the people and the corresponding communication standards with respect to the software development model. 

Agile software delivery process 

In general the software delivery process implemented across the Agile project management is very rapid and accurate when compared to other existing project management methods. The process of adoption towards the changes in code, project or product is streamlined across the Agile framework and also includes many techniques to handle the changes in the requirements or the complete products in an easy manner without much sophistication and complexity. In general the Agile process can be divided in to three important aspects as discussed below and the complete functionality of the Agile can be described with the help of these steps 

1. Agile is incremental and Evolutionary, where the changes related to the internal and external environment can be easily adopted
2. Agile is modular and lean, where the process involved in developing the software can be easily modified as per the requirements of the users and stakeholders
3. Agile is time based, where the iterative methodology is implemented across the software development process and also includes the feedback loops and progress checkpoints.

Managing the change across the software development can be considered as the tedious job to be handled and in general most of the organizations fail at this stage. In general handling the change is not a problem, as the world is changing continually and thus the requirements from the client also changes in a very natural manner. Handling the changes from the client involves lot of issues and requires a perfect plan and proper change management methodologies to achieve success in delivering the required changes as per the client requirement.

In general the changes across the software development can be of either liner or non-liner and handling the liner changes is not a great deal and the main issues raises when the changes or of radical and non-linear and most of the change management procedures fail at this level. Agile can be considered as the best project management method that can be used to handle these types of changes in a convenient manner. Agile provides a perfect methodology to handle the changes in the requirements and ensure a rapid delivery of the software without any further issues. 

Research methodology 

In general the research methodology can be of either qualitative or quantitative based on the research being done. Quantitative research methodology is done to proceed with this research and an empirical investigation is done towards different software development models in place for a successful delivery of the project. Each and every software development model is reviewed and compared against the process followed and a comparison is done with the agile framework to evaluate the importance of agile framework.

As the main aim of this project is to understand and review the importance of agile project management model, secondary source of information is used across the research. Gathering the primary source of information is really tough across this project, as access to the organizations which are using Agile framework is not provided. Thus primary source of information in the form of interviews or semi structured interviews is not possible in this context and thus I would like to use only secondary source of information to proceed with this research. The required secondary source of information is gathered from different websites, articles and journals and few of them are listed as below. To test the validity of the research done, agile scrum methodology is reviewed initially and compared with the existing models like water fall model and V model.

 Project plan 

Task	Description	Start Date	End Date	Duration
Introduction	Basic introduction to the project along with the problem definition and aims and objectives are defined in this section.			2 weeks
Literature review	Following tasks are covered across literature review Introduction to software development process Review of existing software development  models Analysis of the advantages and limitations of the existing models Introduction to Agile Review on Agile framework			4 weeks
Research analysis	Following aspects are covered under this section Analysis on Agile software development model Analysis on Scrum methodology Analysis on different Agile methodologies against various stages of software development Agile design and testing aspects			4 weeks
Research findings	Following tasks are covered under this section  Review on main activities of scrum Main artifacts of scrum methodology Review on main roles on a scrum methodology team Analysis on Managing backlogs – measuring customer value			3 weeks
Conclusion and Future work	Overall conclusion to the work done and the future recommendations are covered in this chapter			1 week

Project title:  A Model for Content Based Image Retrieval System

Introduction:

The advanced technologies in the image compression and retrieval techniques have a lot of research interest in recent years, especially for Content-Based Image Retrieval System (CBIR). Content-Based Image Retrieval System focus on the retrieval of image within a large collection of images by assuming the query given by the user. The main purpose is to develop fast and efficient strategy to retrieve the query concept. 

Early research in image retrieval technique has been focused only on low-level vision. At these stages, Images were first annotated with text and then searched using a text based approach from the traditional database system. It also named as a keyword annotation, which is a natural extension of text retrieval. Unfortunately, after years of research, the retrieval performance is still far from user’s expectations. There will be lot of disadvantages like speed of image retrieval is very slow, inconsistency and not reliable while using a text based image retrieval system. These past experiences have made it clear that learning techniques need to be integrated into the retrieval system. Learning is a general concept and it can be from statistic models. 

Project Aim:

The aim of the project is to develop and implement a Model for Component Based Image Retrieval System to retrieve an image from the large collection of images in the database system. This kind of strategy will be more useful to the users to find and retrieve the required image as quick as possible from the database

Project Objective:

Core Objective:

To developed system uses the Content Based Image Retrieval (CBIR) Technique in order to retrieve the image from the database system based on the users query given to the system. The users query can be performed in the way such that those images can be classified into several frameworks and retrieved by comparing several classification techniques in the retrieval content.

• Developing a user friendly software system
• Performing the user’s query in the system.
• Retrieving the required images from the system quickly.
• Display the required output to the users.

Advanced Objective:

Although the proposed retrieval model is for CBIR, it can be easily expanded to handle other media types, such as video and audio files. 

Requirements Analysis: 

• Analysis of different interactive image retrieval techniques used in Multimedia applications and using an optimal technique (CBIR) to retrieve the image very quickly.
• Analysis of various image processing methods and the attributes of images which are useful to identify and retrieve those images from the Database system.
• Analysis of suitable queries given by the users related to the dimensions of those images.
• Analysis of various limitations available for the system in order to retrieve an image from the database system.
• Analysis of usability of the system in various fields like Multimedia, Engineering, Medical and Defence, etc. 

Project Plan: 

WRITING	PROGRAMMING AND TESTING	DEADLINES
Literature Study-Background of the Project EPP(Extended Project Proposal)	Study about Programming Concept in C#.NET
Literature Study 2-Project Requirement Analysis. Existing and Proposed System	More Study about .NET with Database
Different Modules of the Project	Planning of various development stages.
Various Components of the project. Submission of Progress Report 1.	Design of Various Class Diagrams-ER diagram and use case diagram.
Description about various components of the project.	Programming for Modules.
Report Preparation 1 Progress Report 2	Programming to interconnect Database system.
Report  Preparation 2	Programming Perform Unit testing
Progress Report 3Final Report preparation and Referencing. .	Testing and Debugging.
Submission of Draft Project Report	Submission of model  Project file  System
Oral Presentation
Project Hand-in Date

 Expected Achievements:

A user friendly software system which performs the following tasks

• Perform Users login verification.
• Performing user’s query in the system.
• Retrieving the required images from the system quickly.
• Display the required output to the users.

System Requirements:

Hardware Requirements:

• System                       : Pentium IV 2.4 GHz
• Hard Disk                  : 40 GB
• RAM                           : 256 MB 

Software Requirements:

• Operating system     :-  Windows XP Professional
• Front End                :-  Microsoft Visual Studio .Net 2005
• Back End                :- My SQL
• Coding Language   : – C# 2005

Questionnaire to Project Managers

• What are the main benefits you observed with Agile framework?
• What is the frequency of your Agile iterations?
• What is the team size involved in the Agile development methodologies?
• How the team does analyze the user requirements documentation?
• How the user stories are created against the user requirements and how they are validated in the meetings?
• How do you use the story points in estimating the project metrics?
• What are the key responsibilities assigned to your scrum master?
• How do you assign the works to the developer and validate the work assigned?
• How frequently does you conduct the sprint meetings and what do you discuss in those meetings
• What is the level of involvement of product owner during the Sprint meetings
• What is the role played by scrum master during the sprint meetings?
• What is the composition of your scrum team in terms of their functionalities?
• Who all are involved in the sprint meetings?
•  How do you compare the Agile scrum methodology to traditional software development models?
• What future plans you have with respect to the implementation of Agile in your organization? 

Title: Implementation of Agile-Scrum Methodology into Software Development

Study Area: Software development and management 

Aim:   To analyze the concept of implementing agile scrum methodology over the pre existing current models in software development to overcome existing development difficulties. 

Objectives

Following are the research objectives of the project

• Gathering the current existing software development models by conducting a survey in software industry.
• Analysis of the Comparison outcome between agile scrum methodology to the existing methodologies (i.e. V model).
• To prove how an Agile-scrum can be iterative, progressive development process leads to efficient delivery of useful software.
• To discuss the importance of agile development method, and implementation of its principles and practices of Scrum technique.
• Managing the Development of a software application at different stages involving Planning, Design, Coding, Testing and Implementation. 

Deliverables

Following are the research deliverables of the project

• Literature review of existing methodologies across the software development industries.
• Adaptive Flow diagrams, Pie Charts and Graphs to educate the need of Agile-Scrum Methodology into current era of software development.
• Production of an Efficient, secured, reliable Software application maintaining industry standards within provided Resources and Timescale.
• Building a software application on DotNet Framework with the use C# Programming, using Agile methodology throughout the development process.
• Maintaining the software quality by usage of Agile Testing methods to maintain industry standards.
• Practical results and observation Reports to enhance Agile-scrum methodology over Pre existing models.           

INTRODUCTION 

           The process of software development for any kind of organization is one of the absolutely vital in order to your software development team members to enable to achieve a better and best software project. The main purpose of software development plan is to accomplish the entire plan which is required in order to build, modify, upgrading and defect free software system while developing detail plans on how each step need to be deployed. It will be covering each and every aspect-right from the project process of software development which is as follows. 

• The tasks which need to be completed in a software development
• The start points and end points of the given tasks.
• Any work  that can be dependent by previous or related to various departments
• Who will be the accountable person for a specified tasks
• Employee support throughout software development testing cycle 

Problem Definition 

           In years back to pursue above given tasks to acquire best software output within given time, software industries use appropriate software development methodologies. For example waterfall methodology. In this strategy software industries have been encountered so many technical and physical problems; implementing this methodology is very use full for small scale industries that cannot spend much money on giant usage software’s. The major disadvantages of this methodology are           

• Once the project in the phase of designing stage of software development is completed, we cannot go back and amend the plan.
• If anything went wrong in initial stage of project phase things can be really disaster at implementation stage.
• When we are in middle of the project if our client needs some amendments to the layout, it cannot be rewritable.
• The biggest disadvantage of this model is until the all project stages complete we won’t be knowing outcome of the plan has succeeded or not.
•  So, some scenarios might be the case outcome of the project what has been design is not exactly what has been asked for. 

As we can see the above problems when we using waterfall methodology into a software development. In order to overcome these problems to achieve best project output and software product what clients and consumers have been looking for in right time within given resources, we have to follow the most advanced and reliable source of methodology such as agile scrum. 

Project Description

       The main objective of this Implementation of Agile-Scrum Methodology project is how agile scrum methodology can be iterative and successful implementation of software methodology for the software development in current modern world, and analyze the concept of implementing agile scrum methodology over the pre existing current models in software development to overcome existing software development difficulties. This below fig is project overview and it is model of entire system.