Here's a definition I found on the Internet (there are many to choose from and we'll see others later in the semester)
The computer science discipline concerned with developing large applications. Software engineering covers not only the technical aspects of building software systems, but also management issues, such as directing programming teams, scheduling, and budgeting
I don't know!
SUBJECT TO CHANGE
bash), etc.find, grep)ant and make)subversion)SUBJECT TO CHANGE
| Monday Lecture | Lab | Friday Lecture |
|---|---|---|
| Homework Assigned | ||
| Homework Due Lab Assigned and Due Following Week |
Quiz Next Homework Assigned |
| Monday Lecture | Lab | Friday Lecture |
|---|---|---|
| Homework 1 Assigned | Lab 0 Assigned and Due | Quiz 0 |
| Labor Day | Lab 1 Assigned, Due Following Week | Quiz 1 Next Homework Assigned |
IMPORTANT: The lab sections for this class will be held in the CSEL. You need to make sure that you have an account on the CSEL machines and that you have Buff OneCard access to the lab BEFORE your first lab section. Fortunately, the process is straightforward.
Your CSEL Accountand then click on the link
Set Buff OneCard Numberand follow the instructions.
Brooks says:
OS/360 was late, took more memory than was planned, costs were several times the estimate, and it did not perform very well until several releases after the first.
In a recent article for InformationWeek entitled What's The Greatest Software Ever Written?, Charles Babcock had this to say about the IBM 360 project
Another example of great programming was IBM's 360 system. The software was written as the first general-purpose computer operating system in 1964. Many of the truths we assume today about software--that simple designs are better than complicated ones, that a few skilled programmers will accomplish more than platoons of them--are captured in Frederick Brooks' book on the project, The Mythical Man-Month (Addison-Wesley Professional, 1995). Brooks already knew how many things could go wrong with big software projects before the 360 project began. In fact, he was a critic within IBM of carrying out the project at all; he thought it had too many potential points of failure. That's why IBM put him in charge of it, I suppose.
Wise that they did. The result was the first computer system capable of running different applications at the same time. It spawned the IBM line of mainframes, which evolved into the 370 Series and present zSeries. To this day, those systems remain backwardly compatible with Brooks' 360 operating system. Which leads me to another attribute of great software: It's got legs. It isn't easily superseded.
Everybody agrees the IBM 360 was one of the greatest pieces of software ever written.