` Lecture 2

CS 151 - Lecture 2

Cover page image

What is Software Engineering?

toolkit

Initial professional education in a curriculum validated by professional society through accreditation
Fitness to practice evidenced by certification or mandatory license
Continuing education / recertification
Member of a professional society
Adheres to a code of ethics

What is science? American Physical Society:

Science is the systematic enterprise of gathering knowledge about the universe and organizing and condensing that knowledge into testable laws and theories.
Not every “science” discipline practices science—particularly not those that have “science” in their name (library science)
What is computer science? computingcareers.acm.org:

Computer science (CS) spans the range from theory through programming to cutting-edge development of computing solutions.
Computer scientist: Researcher in university or industry lab

IEEE Computer Society:

“(1) The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.

(2) The study of approaches as in (1).”
Software Engineering Body of Knowledge (SWEBOK)
Knowledge areas: requirements, design, construction, testing, maintenance, configuration management, engineering management, process, quality, professional practice, economics.

Software development methodology: Framework for planning and controlling the development of a software system
Who does what when?
Will the project finish as planned?

Breaks development process down into multiple phases
Early phases focus on the construction of prototypes
Lessons learned from development of one prototype can be applied to the next iteration
Problem: can lead to many iterations, and process can take too long to complete

Goals
- Identify classes
- Identify behavior of classes
- Identify relationships among classes
Artifacts
- Textual description of classes and key methods
- Diagrams of class relationships
- Diagrams of important usage scenarios
- State diagrams for objects with rich state

You only need these commands:

git clone ssh://server.com/reponame
git pull
git add file
git rm file
git status
git commit -a -m "comment"
git push origin master

You only clone a repo once.
Always run git pull before you do anything else
Run git add to add files to the “staging area”.
Run git commit -a -m "..." to commit the staged files.
Run git push origin master to update the server.
Version control is only for files that are
1. not automatically generated
2. platform-independent
Use .gitignore to list files that should not be checked in (e.g. Java class files).

In the Bash shell, change to the directory that git clone created and make a new directory lab2.
```
cd cs151 # or whatever your repo is named
mkdir lab2
```
Make a file lab2/report.txt and put something into it (like Hello, World! or whatever).
Type git status. What do you get? (Paste that into your report.)
Type git add lab2/report.txt and again git status. What happens? (Paste that into your report and save the file.)
Type git commit -a -m "Added lab2" and again git status. What happens? (Paste that into your report.)
Type git push origin master and again git status. What happens? (Paste that into your report.)
In the BitBucket web interface, locate the report.txt file. Take a screen shot. Add it into the lab2 directory. What do you need to do to make it appear in the web interface? (Put the answer into your report.)

Add the Greeter.java and GreeterTester.java files to the lab2 directory.
Compile them and run GreeterTester. What happens?
Run git status. What happens?
We don't want to add the .class files to the repo. Create a file .gitignore in the base directory of your repo (probably ~/cs151). Note that the file name starts with a period. Add the line
```
**/*.class
```
Run git status again. What happens? Why?
Now add the source files to the repo and push them to the server. How did you do that?
Push your report with the answer to the preceding question. Check in the BitBucket web interface that it got there.
Now you know everything that you need to know about Git to submit your homework!