Computer Programming System Development Life Cycle
computer programming system development life cycle
Question of programming for professionals only?
I have degree in computer science from the University in August 2006. E minor was in the system information mangement. I'm not interested in programming for coding. But as management positions are not as available, I look for programming / coding. I have some questions. I just try to give me an idea. 1. What is "to develop a test plan, test execution, the test site, testing thoroughly. "? 2. How much knowledge is necessary to say" domain C Sharp Microsoft SQL Server 2005 as database "and" designing reports with Crystal Report in C Sharp? "Or where I can get this knowledge? 3. What it means to have a sound knowledge on "object-oriented architecture and design" and "Microsoft Dot Net Framework" and "all stages of life development software "(in theory or coding)?
1. When you are finished with a change, it is necessary First test the changes just to make sure that not only does what is supposed to do, but that does not destroy existing functionality. You not imagine how you will test your changes. Tell yourself Adding a column to a table in an HTML form. Therefore, you should come to different test scenarios. Say this column displays the data in a field in the database and this field is optional, which means that this field can be empty sometimes. These are the scenarios that you need to test, i) A person who records field of population to its application. ii) A person with this domain the population is connected to your request. And then you come up with a plan as detailed below, a person could connect with username, whatsoever, and password, either. Click on a link in the navigation bar to open any application. And then he / she is the additional column to next to any field. As for testing Web and back-end test, the test plan for a person who has to prove the change. Never really seen someone almost always hit your application at any given time. You probably have several people hitting the application and database simultaneously. Is your server can handle thousands of concurrent users? Your database is capable of handling multi-threading solutions? 2. C # (pronounced C Sharp) is Microsoft's attempt to compete with Java. C # is also one of the ASP language. Net use. ASP means Active Server Pages. ASP, ASP. Net, ColdFusion, PHP, JSP (Java Server Pages) are used for server-side programming. These languages enable you to develop dynamic Web applications that interact with a database, web services, RSS feeds, items … and many other server-side technologies. There are many popular selections such as server basis (ie MS SQL Server, Access, MySQL, etc …) MS SQL and MySQL are mainly used for enterprise-level applications. Crystal Reports is the most technologically popular for the report and graphic effects. Use C # to generate a Crystal Report based on the parameters on the fly. To learn more about it, you can go anywhere in major bookstores like Borders or Barnes and Noble to read about ASP. Net, C #, MS SQL and Crystal Report. 3. If you got a degree in computer science comes two years you need to know what the object-oriented architecture (OOA) is. I have my degree in computer science in 1997. FOO was a big problem at the time and has become an architecture of great interest. It is difficult to explain in detail what is FOO because there would be enough space for it. I guess I had some C + + classes in college. C + + is an object-oriented language. Say you have to plan something about a car. A car is an object. There are many attributes associated with a vehicle (Object). A car door, silent, engine, etc. … A car can move forward, backward, turn left, turn right, etc … You can define a car as an object that has all these attributes. Therefore, when you say A_car = New Car (). A_car is defined as a car with all the attributes associated with a car. Microsoft. Net Framework is even more difficult to explain. You can go to any bookstore important to read. Regarding the life cycle of software development, each time to a project, rather but to go ahead and make the change, the need to create a specific kind of first explaining how the project would come out. I know you do probably never done anything like this when I was in college. This specification covers the following i) Analysis: What equipment is needed this change, so staff must be involved, which is in scope, which is out of range, etc … ii) The purpose of this project. iii) What exactly are changes involved in this project. Flowchart of the application. If it was a change in an existing application, you must show comparisons of the existing application and implementation of its changes. Users have a different experience in the new application? It would be nice to have a model with screenshots. iv) When the changes are completed, how will you test the changes? How will you get the changes in production? Who needs to test the changes? The point of creating a specification is to your customers to see what is actually done. This does not begin the actual development until the specification is approved by their customers. Many times, customers can request a change I think it's a simple change (As they are not computer programmers) to your program may not be as easy for you. Before the actual development work, all changes made to the specification, making it just re-write and not much time to talk in relative terms. When the specification is approved, you will build your application specifications. If your customers notice the change, may point to the specification.