I am planning to develop a C# application for my client. I need advices from well experienced dot net guys with restpect to SDLC.
I want the walk thorugh of the project , which are the different steps that needs to be followed?
Application is to parse the body of the email and put the filterd data into the excel file.
Please advice me experts !! :-)
How are you planning on developing? Waterfall? Agile? Prince2?
There are many methodologies, and your first step is to select one. There are just too many options for a coherent answer to be given to your question.
SDLC is very related to team layout. If you are the only person writing this application, and the scope is limited I would white board your project first. Draw some boxes write down some object names. Then write a series of tests for your public interfaces. Start writing some code once you get your first tests to pass look over your code and refactor.
If you have more then you working on your project you need to decide a methodology you want to follow, and lead your team that way.
First, I'd say that the most important step is to meet and listen to your client. He/she's the one that wants something, and most of the time, this something isn't very clear. Be sure to meet with him/her many times during the development process, to be sure that what you're doing is what he/she wants.
Once you know about his/her needs, try to explore the different solutions, like "Developping from 0, Developping from an already existing software", etc. If it looks like it will take less time to modify a software to match his/her needs, try to do so. YOu might save alot of trouble for yourself here.
Once you've started programming, start by doing an interface, then verify if the client likes it. If you seem to be lacking certain functionalities the client might want, you'll know then.
Continue to program and regularly meet your client. Eventually, you'll be done.
I'm insisting on meeting your client, because if you think you've understood what your client wants, work several months on the project, finally show it to your client to only then realise that you were wrong... you get the idea.
Hope that helps.
The basic principles of C# application development are What you need to understand are the bsaic principles of Agile software development.
Predecessors
Jeff Sutherland, one of the developers of the Scrum agile software development process Incremental software development methods have been traced back to 1957.[2] In 1974, a paper by E. A. Edmonds introduced an adaptive software development process.[3] So-called "lightweight" software development methods evolved in the mid-1990s as a reaction against so-called "heavyweight" methods, which were characterized by their critics as a heavily regulated, regimented, micromanaged, waterfall model of development. Proponents of lightweight methods, and now agile methods, contend that they are a return to development practices from early in the history of software development.[2] Early implementation of lightweight methods include Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic Systems Development Method (DSDM) (1995). These are now typically referred to as agile methodologies, after the Agile Manifesto published in 2001.[4] [edit]Agile Manifesto In February 2001, 17 software developers[5] met at a ski resort in Snowbird, Utah, to discuss lightweight development methods. They published the Manifesto for Agile Software Development[1] to define the approach now known as agile software development. Some of the manifesto's authors formed the Agile Alliance, a non-profit organization that promotes software development according to the manifesto's principles. Agile Manifesto reads, in its entirety, as follows:[1] We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
Agile software development poster Twelve principles underlie the Agile Manifesto, including:[6] Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Working software is the principal measure of progress Even late changes in requirements are welcome Close, daily cooperation between business people and developers Face-to-face conversation is the best form of communication (co-location) Projects are built around motivated individuals, who should be trusted Continuous attention to technical excellence and good design Simplicity Self-organizing teams Regular adaptation to changing circumstances In 2005, a group headed by Alistair Cockburn and Jim Highsmith wrote an addendum of project management principles, the Declaration of Interdependence,[7] to guide software project management according to agile development methods. [edit]Common characteristics
Pair programming, an agile development technique There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project. Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders. This helps minimize overall risk, and lets the project adapt to changes quickly. Stakeholders produce documentation as required. An iteration may not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration.[8] Multiple iterations may be required to release a product or new features. Team composition in an agile project is usually cross-functional and self-organizing without consideration for any existing corporate hierarchy or the corporate roles of team members. Team members normally take responsibility for tasks that deliver the functionality an iteration requires. They decide individually how to meet an iteration's requirements. Agile methods emphasize face-to-face communication over written documents when the team is all in the same location. When a team works in different locations, they maintain daily contact through videoconferencing, voice, e-mail, etc. Most agile teams work in a single open office (called a bullpen), which facilitates such communication. Team size is typically small (5-9 people) to help make team communication and team collaboration easier. Larger development efforts may be delivered by multiple teams working toward a common goal or different parts of an effort. This may also require a coordination of priorities across teams. No matter what development disciplines are required, each agile team will contain a customer representative. This person is appointed by stakeholders to act on their behalf and makes a personal commitment to being available for developers to answer mid-iteration problem-domain questions. At the end of each iteration, stakeholders and the customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment and ensuring alignment with customer needs and company goals. Most agile implementations use a routine and formal daily face-to-face communication among team members. This specifically includes the customer representative and any interested stakeholders as observers. In a brief session, team members report to each other what they did the previous day, what they intend to do today, and what their roadblocks are. This standing face-to-face communication prevents problems from being hidden. Agile emphasizes working software as the primary measure of progress. This, combined with the preference for face-to-face communication, produces less written documentation than other methods. The agile method encourages stakeholders to prioritize wants with other iteration outcomes based exclusively on business value perceived at the beginning of the iteration. Specific tools and techniques such as continuous integration, automated or xUnit test, pair programming, test driven development, design patterns, domain-driven design, code refactoring and other techniques are often used to improve quality and enhance project agility. [edit]Comparison with other methods
As found at: