28-05-2013, 01:04 PM
A MINI-PROJECT REPORT ON DIGITAL CALENDAR
DIGITAL CALENDAR.doc (Size: 506.5 KB / Downloads: 135)
Introduction of desinging language
We think, this program will be good explanatory for new users. This is totally based on the programming language C.
Also this text editer follows the very basic model of software development method that is the waterfall model.Let us take little attention towards the c language.
C-LANGUAGE
C is a general-purpose computer programming language developed in 1972 by Dennis Ritchie at the Bell Telephone Laboratories for use with the Unix operating system.
Although C was designed for implementing system software, it is also widely used for developing portable application software. Despite its low-level capabilities, the language was designed to encourage machine-independent programming.
INTRODUCTION OF CALENDER
A calendar is a system of organizing units of time for the purpose of reckoning time over extended periods. By convention, the day is the smallest calendrical unit of time; the measurement of fractions of a day is classified as timekeeping. The generality of this definition is due to the diversity of methods that have been used in creating calendars. Although some calendars replicate astronomical cycles according to fixed rules, others are based on abstract, perpetually repeating cycles of no astronomical significance The common theme of calendar making is the desire to organize units of time to satisfy the needs and preoccupations of society. In addition to serving practical purposes, the process of organization provides a sense, however illusory, of understanding and controlling time itself. Thus calendars serve as a link between mankind and the cosmos
According to a recent estimate (Fraser, 1987), there are about forty calendars used in the world today. This chapter is limited to the half-dozen principal calendars in current use. Furthermore, the emphasis of the chapter is on function and calculation rather than on culture.
Software development process-
A software development process is a structure imposed on the development of a software product. Synonyms include software life cycle and software process. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. The largely growing body of software development organizations implement process methodologies. Many of them are in the defense industry, which in the U.S. requires a rating based on 'process models' to obtain contracts.
The international standard for describing the method of selecting, implementing and monitoring the life cycle for software is ISO 12207.
A decades-long goal has been to find repeatable, predictable processes that improve productivity and quality. Some try to systematize or formalize the seemingly unruly task of writing software. Others apply project management techniques to writing software. Without project management, software projects can easily be delivered late or over budget. With large numbers of software projects not meeting their expectations in terms of functionality, cost, or delivery schedule, effective project management appears to be lacking.
Planning-
The important task in creating a software product is extracting the requirements or requirements analysis. Customers typically have an abstract idea of what they want as an end result, but not what software should do. Incomplete, ambiguous, or even contradictory requirements are recognized by skilled and experienced software engineers at this point. Frequently demonstrating live code may help reduce the risk that the requirements are incorrect.
Once the general requirements are gleaned from the client, an analysis of the scope of the development should be determined and clearly stated. This is often called a scope document.
Deployment and maintenance-
Deployment starts after the code is appropriately tested, is approved for release and sold or otherwise distributed into a production environment.
Software Training and Support is important because a large percentage of software projects fail because the developers fail to realize that it doesn't matter how much time and planning a development team puts into creating software if nobody in an organization ends up using it. People are often resistant to change and avoid venturing into an unfamiliar area, so as a part of the deployment phase, it is very important to have training classes for new clients of your software.
Other models-
Capability Maturity Model Integration-
The Capability Maturity Model Integration (CMMI) is one of the leading models and based on best practice. Independent assessments grade organizations on how well they follow their defined processes, not on the quality of those processes or the software produced. CMMI has replaced CMM.
ISO 9000-
ISO 9000 describes standards for a formally organized process to manufacture a product and the methods of managing and monitoring progress. Although the standard was originally created for the manufacturing sector, ISO 9000 standards has been applied to software development as well. Like CMMI, certification with ISO 9000 does not guarantee the quality of the end result, only that formalized business processes have been followed.
ISO 15504-
ISO 15504, also known as Software Process Improvement Capability Determination (SPICE), is a "framework for the assessment of software processes". This standard is aimed at setting out a clear model for process comparison. SPICE is used much like CMMI. It models processes to manage, control, guide and monitor software development. This model is then used to measure what a development organization or project team actually does during software development. This information is analyzed to identify weaknesses and drive improvement. It also identifies strengths that can be continued or integrated into common practice for that organization or team.