27-08-2014, 12:50 PM
The Avtar Bani is the religious book of Nirankari Mission that outlines the key philosophy of Sant Nirankari Mission. It may infact be considered the Bible or Quran of the Mission. The Sant Nirankari Mission also known as Universal Brotherhood Mission, is a spiritual organisation.The Sant Nirankari Mission is neither a new religion nor a sect of an existing religion, but an all embracing spiritual moment dedicated to human welfare.Its objective is to establish Universal Brotherhood among people from diverse backgrounds throughout the world. This project will help the Nirankari devotees to stay in touch with the latest happenings of the Sant Nirankari Mission around the globe.The project can run only on Apple mobile products and having iOS 6.0 or later.
The AvtarBani is the religious book of Nirankari Mission that outlines the key philosophy of SantNirankari Mission.It may infact be considered the Bible or Quran of the Mission.
The SantNirankari Mission also known as Universal Brotherhood Mission, is a spiritual organisation.TheSantNirankari Mission is neither a new religion nor a sect of an existing religion, but an all embracing spiritual moment dedicated to human welfare.Its objective is to establish Universal Brotherhood among people from diverse backgrounds throughout the world.
His Holiness Baba Hardev Singh JiMaharaj is the head of SantNirankari Mission. Today, SNM has over 12 million followers all over the world.Its world headquarters is located in SantNirankari Colony,Delhi.
The iPhone App contains the following features
· English versions of AvtarBani.
· Hindi versions of AvtarBani.
· Punjabi versions of AvtarBani
· Notes option to add a note to the Verses.
· Bookmark option to save your favourites.
· Option to adjust Font Size and background color.
· Live News feed from Nirankari.org.
ii. Scope and Objective of Project
Normally, a verse from the AvtarBani is read out before every discourse in most congregations (except when His Holiness Himself is giving the discourse) . The verses are also read out at the beginning of each congregation.Devotees are however free to sing/read these verses as hymns anytime they prefer for personal spiritual enlighten.
It contains 376 hymns which describes the qualities of Formless God (Nirankar), the important role of a True Spiritual Guide in attaining God realization, the kindness and the grace of the True Master, the purpose of human life, five fundamental principles, true devotion and how a man can lead a saintly life.The AvtarBani is not worshipped as Holy Religious Book like the Quran or The Bible, but it is highly regarded by the Nirankari devotees for its authenticity.
This project will help the Nirankari devotees to stay in touch with the latest happenings of the SantNirankari Mission around the globe.
2. System Study & Problem Formulation
i. Existing System:
The SantNirankari Mission also known as Universal Brotherhood Mission, is a spiritual organisation.TheSantNirankari Mission is neither a new religion nor a sect of an existing religion, but an all embracing spiritual moment dedicated to human welfare.Its objective is to establish Universal Brotherhood among people from diverse backgrounds throughout the world.
This project is useful to those devotees who are currently using iOS devices .This project will give them access to read hymns and can able to record their voice or even can write notes . These notes or voices are stored in the database and iPhone document directory.
ii. Limitation of Existing System :
· Works on iOS 6.0 onwards
· Need any iOS based device
· Can.t work on any hardware or device
· Project can be downloaded from only iTunes
iii. Proposed System :
The project will include the following features :
· English versions of AvtarBani.
· Hindi versions of AvtarBani.
· Punjabi versions of AvtarBani
· Notes option to add a note to the Verses.
· Bookmark option to save your favourites.
· Option to adjust font size and background color.
· Live News feed from Nirankari.org.
· Voice recording functionality.
iv. Advantages of Proposed System :
· Information can be accessed at any time.
· Highly user-friendly
· Enterprise independent
· Cross-platform
· Easy-to-use
· Ease of Information for Students
· Tested system to track unnoticed error
· Data entry restricted to valid domains to avoid errors
v. Feasibility Study:
A feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out a designated task. Generally, a feasibility study precedes technical development and project implementation.
A feasibility study is a test of a system proposal according to its workability impact on organization, ability to meet user needs and effective use of resources. The objective of a feasibility study is not to solve a problem but to acquire a sense of its scope. In other words, a feasibility study is an evaluation or analysis of the potential impact of a proposed project.
Feasibility study was done in three phases documented below:
A: Economic feasibility: Economic feasibility is the most frequently used method for evaluating the effectiveness of the candidate system. More commonly known as costenefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with the costs. If benefits outweigh the costs, then the decision is made to design and implement the system. A costenefit analysis was done for the proposed system to evaluate whether it would be b economically viable or not.
· Cost-based study: It is important to identify cost and benefit factors, which can be categorized as follows: 1. Development costs and 2. Operating costs. This is an analysis of the costs to be incurred in the system and the benefits derivable out of the system.
· Time-based study: This is an analysis of the time required to achieve a return on investments. The future value of a project is also a factor.
B: Technical feasibility:Technical feasibility centers on the existing computer system. (Hardware/software) and to what extent it can support the proposed addition also the organization already has sufficient high-end machines to serve the processing requirements of the proposed system. So there is no need to purchase new software as the organization has necessary software i.e. eclipse, SQL Server etcor hardware to support the proposed system.
C: Behavioral feasibility: People are inherently resistant to change and computers have been known to facilitate change. There is always some reluctance among the users against the introduction of new system but they were told that this system would eliminate the unnecessary overhead of database migration and conversion, which presently had to be carried out on daily basis to facilitate transactions between the different departments. The objective this feasibility phase is to take the operational staff into confidence.
3. Project Plan
i. Team Structure :
The team structure of the team plays a critical role in its success. Software development teams function best when they are organized into small sub teams.
There should be clear delegation of responsibilities to sub teams. Team organization structure is largely determined by the resources available.
Consider three types of organization structures:
· Generalist structure: Sub teams consist of individuals with a broad range of experience. These teams typically manage end-to-end development of artifacts.
o Advantage: There is greater continuity of artifact ownership throughout the project and enhanced focus on the improvement of the system as a whole. Project Management is simplified by the ability of generalists to understand one another.s roles and responsibilities, which facilitates more effective communication and cooperation. Software traceability is easier to accomplish.
o Disadvantage: Problems which require a high level of specialty expertise are more difficult to address. There may be less focus on improvement of the individual parts which make up the system as a whole. Project management may increase in difficulty due to inability of generalists to complete within time and budget constraints those tasks which require specialist expertise.
· Specialist structure: Sub teams consist of specialists. These teams typically work on several artifacts, focusing on the aspects which align with their specialty.
o Advantage: Aspects requiring special expertise are dealt with more efficiently and effectively, resulting in a higher quality of work for all the distinct parts which make up the system as a whole.
o Disadvantage: Sometimes the focus on improving a specific part of the system a specialist is responsible for does not improve the system as a whole. Lack of continuity in ownership can result in problems ranging from scope creep to developing components which are not well suited for the final software product. Communication and cooperation is less effective between specialist sub teams which don.t always understand each other.s roles and responsibilities. Software traceability is more difficult.
· Hybrid structure: Both generalist and specialist sub teams exist. Generalist sub teams oversee end-to-end development of artifacts. They also work with specialist sub teams responsible for the aspects of the artifact which align with their specialty.
o Advantage: Generalists improve the continuity of artifact ownership and maintain focus on building functional parts which easily integrate to form the system as a whole. Generalists also improve communication and cooperation between specialist sub teams. Specialists increase the quality of the individual parts and provide the ability to dealwith specialty problems efficiently and effectively.
o Disadvantage: Finding the resources to create hybrid teams is more difficult and costly. Project management may increase in complexity when managing both vertical and horizontal sub teams. Additionally, while well organized hybrid teams tend to provide the best of both worlds, poorly organized hybrid teams can just as easily bring out the worst of both worlds.
ii. Development Schedule :
While focusing on the development of the project, the methodology being adopted by the organization plays an important role.
Here we have implemented Agile Methodology. The Agile movement proposes alternatives to traditionalproject management. Agile approaches are typically used in software development to help businesses respond to unpredictability.
The important part of this methodology is Scrum.
What is Scrum?
Scrum is the most popular way of introducing Agility due to its simplicity and flexibility. Because of this popularity, many organizations claim to be “doing Scrum” but aren.t doing anything close to scrum.s actual definition.Scrum emphasizes empirical feedback, team self management, and striving to build properly tested product increments within short iterations.
Scrum has only three roles: Product Owner, Team, andScrum Master. The responsibilities of thetraditional project manager are split up among these three Scrum roles. Scrum has five meetings: Backlog Grooming, Sprint Planning, Daily Scrum, the Sprint Review Meeting and the Sprint Retrospective Meeting..
Why Agile?
Agile development provides opportunities to assess the direction throughout the development lifecycle. This is achieved through regular cadences of work, known as Sprints or iterations, at the end of which teams must present a potentially shippable product increment. By focusing on the repetition of abbreviated work cycles as well as the functional product they yield,agile methodology is described as “iterative” and “incremental.” In waterfall, development teams only have one chance to get each aspect of a project right. In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited. When a team stops and re-evaluates the direction of a project every two weeks, there.s time to steer it in another direction.
This “inspect-and-adapt” approach to development greatly reduces development costs and time to market. Because teams can develop softwareat the same time they.re gathering requirements, “analysis paralysis” is less likely to impede a team from making progress. And because a team.s work cycle is limited to two weeks, stakeholders have recurring opportunities to calibrate releases for success in the real world. Agile development helps companies build the right product. Instead of committing to market a piece of software that hasn.t been written yet, agile empowers teams to continuously replan their release to optimize its value throughout development, allowing them to be as competitive as possible in the marketplace. Agile development preserves a product.s critical market relevance and ensures a team.s work doesn.t wind up on a shelf, never released.