[Dedicated to the memory of Professor Phil Dorin, teacher, mentor and friend.]
Design, development, and management issues of large-scale software systems which are reliable and easily maintainable, using methodologies applicable to evolving requirements through collaboration between self-organizing, cross-functional teams. A course project covers each step of the development process from the initial needs analysis and requirements specification through design and implementation. Tradeoffs between agile and older approaches, the impact of legacy systems, architectural representation issues, testing, project risk management, and emerging trends in software engineering such as model-driven engineering and aspect-oriented software development [are covered].
It is not assumed that students have extensive programming experience for this class. The focus of the semester project is the management processes that are used to ideate, design, implement, test, and review an Agile project. While you WILL need to do at least SOME programming to implement the project, it does NOT have to be extensive or sophisticated, as long as good software development practices are followed, and as long as the student teams follow and document their Agile method of project management.
Note that the course description above from the LMU Bulletin is not very specific.... there is more detail below!
The goal of this course is to learn the concepts and issues related to the Agile Software Development process, along with related Project Management topics. Instruction and comparisons to the existing Waterfall method will be made, along with contrasts to other development life cycle models. The topics covered include [but are not limited to] the following:
When you finish the course, you will be able to:
In accordance with the LMU Credit Hour Policy, this 3-unit course will require 9 hours of work per week, which includes the time spent in class and lab sessions. This work will consist of homework, a project, watching and commenting on some videos about databases and related topics, and reading/study of textbook material.
In a nutshell, here's what you'll need to do to be successful in this course.
…and *I* promise to:
There are two required textbooks for this course:
There is one optional textbook for this course:
YOU WILL NEED ACCESS TO THESE BOOKS FOR THE CLASS!
ONLY THE FIRST BOOK IS AVAILABLE IN THE LMU BOOKSTORE. The other two books are not available in the bookstore. However, they are available at many other fine retail outlets, both online and brick-and-mortar. We will be using them for homework assignments, general reading and information, as well as tutorials for using several different project management tools and Agile methodologies both in and out of the classroom. The titles of the books provide you with their contents and focus.
Although we won't be covering the books in their entirety for this class, we will be using them as primary resources. It is up to the student to read the book and be prepared for the class, including answering questions about the chapter material.
There is also a large number of other resources which can be used to "mine the gold" for related information about Agile development and Agile project management. The topic is a very broad field, which has been around for a long time. You may even be required to use the LMU library, [GASP!!] so be prepared!
A list of topics that are covered, and the approximate order and time frame in which they will be discussed, is available on the class notes page for this site.
Chapter readings from the text books and the dates by which these readings should be completed are listed below. Note that you should have read the chapter material prior to the date listed, and you should be ready to discuss the text, ask questions about the concepts, and begin working with some of the implementations of the concepts in class. It is also a good idea to at least read (or preferably try) the exercises contained in and at the end of each chapter.
Here is the reading list:
All written homework assignments are due at the beginning of the class on the date
they are due. Deviation from this process requires prior consent of the instructor.
I left my
homework at home is not a valid reason for late work. Every effort is made to ensure assignments,
required deliverables, and due dates are prominently posted on these pages; it is your
responsibility to make sure you know what is due and when it is due.
You may certainly turn assignments in late; I will happily accept them, but they will be reduced in
grade by one letter for each day they are late.
class day; an
A+ homework due on Thursday which is not
turned in until the following Tuesday will unfortunately only earn a failing grade, unless some prior
arrangements are made with the instructor due to illness or some major schedule conflict. However,
if you want to turn something in late, I'll still provide feedback even for assignments which have no
chance of any credit; I keep this policy to allow you to get the learning benefit of the assignment
even if you don't get a grade for it. My philosophy is that it is important for the students to know
the material, even if an assignment doesn't get the best marks.
Some assignments may be required to be turned in as hard-copy. These must be printed on a printer. All assignments must use proper American English and/or Programming Language spelling and grammar. Failure to do so may cost you up to a letter grade, so get a spell-checker and a grammar checker, or find a friend who is proficient to proofread your work before it is submitted.
Other than these simple rules, there are no requirements for formatting, fonts, colors, diagrams, or anything else with respect to your homework assignments, other than good code craftsperson-ship.
There will be three homework assignments during the semester, due on the dates shown in the list below. Each assignment will contain eight to ten written problems, and some reading and other information/activities such as web sites to browse, articles to read (and possibly write about), or videos to watch. Each of these assignments is detailed on a separate web page; they are available by using the links in the list. Solutions will be provided after the assignments are handed in.
There will be a mid-term during the semester, scheduled for Tuesday of week seven. Note that the test is interspersed with the homework assignments, such that there will not be any homework assignment due on a test date.
There will NOT be a final exam. The semester project will take the place of the final.
There will be a semester development project, which will implement a project of your own choosing that will also include a significant Agile Project Management component. You will pick the application, and will decide which Agile methodology and project management tool[s] you will use to implement it. You will be documenting the project in full, per the requirements on the project page. That page also includes several suggestions for projects which you may use. You will be required to demonstrate certain basic functionality of your work. Demonstrations will be a presentation at the end of the semester, which will occur two weeks before final exam week, during normal class time.
Missed quizzes or tests: it is the responsibility of the student to provide an adequate advance notice to the professor if a scheduled quiz or test is going to be missed. If you have a conflict in schedule which will cause a missed exam, please notify the professor at least two days in advance, if possible, to avoid a failing grade for the exam. Prior arrangements must be made in order for a make-up exam to be taken, since this situation requires the professor to create a second different copy of the exam/quiz/test.
You will need access to a computer of some variety.
If you don't have a computer available, let me know and I will try to work with Masao to get something set up for you using a VPN to a computer in the Keck Lab on campus. You'll still be remote, but you'll have access to SOMETHING to work on. In the best of all possible worlds, we will all have super-duper computing engines to use, but we're obviously not there yet…
Although attendance is not mandatory, it is in your own best interest to attend every class. Much of the material will be discussed and elaborated upon in class, so counting on the books or web pages for all required information will not necessarily provide you with complete information. In addition, there may be in-class exercises in small groups which you will miss out on if you are not there.
Obviously, if you skip too many classes, you will likely fail; this is a simple and self-fulfilling prophecy.
The class participation rubric appears with the grading stuff in the tables below.
There will be no extra credit given in this course.
Grades for the course are assigned according to the weighting factors shown in the tables below.
Final letter grades will be assigned based on the following scale:
|Percent||Letter||Rating and Achievement|
|91 - 100%||A / A-||Professional quality work; outstanding|
|81 - 90%||B+ / B / B-||Entry-level quality work; above average, shows extra effort and interest|
|71 - 80%||C+ / C / C-||Satisfactory work; expected with reasonable effort|
|61 - 70%||D||Substandard work; minimal effort shown|
|60 or less||F||Thank you for playing; see you next semester|
|Development Project |
[ 5% Requirements / Discription]
[ 5% User Stories/Story Points]
[ 5% Project Sprint Planning]
[ 5% Burn-down Plan]
[ 5% Sprint Tracking]
[10% Project Presentation]
[10% Project Implementation]
[10% Management Implementation]
|55% for all|
|Class Participation Criteria||Value|
|Absent *without* prior notification/agreement of professor||0|
|Absent *with* prior notification/agreement of instructor||3|
|Demonstrates excellent preparation with respect to readings and other materials;|
Offers pertinent analysis, synthesis, and evaluation; puts together pieces of the discussion to develop new approaches that take the class further.
Also of note…
An incomplete will be granted only when the student requesting the incomplete has completed at least 80% of the coursework, and has at least a B average in the course work completed. This is standard LMU policy.
Leave of Absence/Withdrawal Policy:
Please read the revised policy in the University Bulletin.
All work is evaluated for both technical merit and quality of written and/or oral presentation.
Find yourself a good spelling and grammar checker, or a trusted human editor, if you
are having any difficulty with the rules of standard English language usage. Another excellent resource
is the Academic Resource Center, located
on the south side of Daum Hall. The center takes appointments, and also allows drop-in consultation
sessions, and they have a number of good benefits. Call (310) 338-2847 to schedule an appointment.
(For those that don't know, Daum Hall is the building where the LMU Security and Parking office used to
be. ARC is on the second floor.)
Another thing to remember is, your coding style is an important part of your assignment evaluations. I WILL NOT HESITATE to take points off for code that has hard-coded number
FAIR WARNING!!! DANGER WILL ROBINSON!!! FAIR WARNING!!!
FAIR WARNING!!! DANGER WILL ROBINSON!!! FAIR WARNING!!!
Student feedback on this course provides valuable information for continued improvement. All students are expected to fairly and thoughtfully complete a course evaluation for this course. All course evaluations for the Seaver College of Science and Engineering are administered online through the Blue™ evaluation system. You will receive an e-mail notification at your Lion e-mail address when the evaluation form is available. You may also access the evaluation form on Brightspace during the evaluation period. A few minutes of class time will be reserved for you to complete a course evaluation near the end of the semester. Please bring a laptop, smart phone, tablet or other mobile device to class on this date so that you can access the online evaluation platform.
Loyola Marymount University is a community dedicated to academic excellence, student-centered education, and the Jesuit and Marymount traditions. As such, the University expects all members of its community to act with honesty and integrity at all times, especially in their academic work. Academic honesty respects the intellectual and creative work of others, flows from dedication and pride in performing one's own best work, and is essential if true learning is to take place. As an LMU Lion, by the Lion's Code, you are pledged to join the discourse of the academy with honesty of voice and integrity of scholarship.
Academic dishonesty will be treated as an extremely serious matter, with severe consequences that can range from receiving no credit for an assignment or test to failing the class, to expulsion.
unauthorized useand, therefore, prohibited
Students with special needs who require reasonable modifications, special assistance, or accommodations in this course should promptly direct their request to the Disability Support Services [DSS] Office. Any student who currently has a documented disability [ADHD, Autism Spectrum Disorder, Learning, Physical, or Psychiatric] needing academic accommodations should contact the DSS Office [Daum Hall 2nd floor, 310-338-4216] as early in the semester as possible. All discussions will remain confidential. Please visit http://www.lmu.edu/dss for additional information.
Students should also keep in mind that resources are available through the Library [https://library.lmu.edu] and Information Technology Services [https://its.lmu.edu]. The DSS Office can help students connect with the appropriate person at the Library and ITS.
As an LMU Lion, by the Lion's code, you are pledged to join the discourse of the academy with honesty of voice and integrity of scholarship and to show respect for staff, professors, and other students.
The following LMU documents are available to reference:
For more information on this or any other conduct issues, please refer to the Student Codes and Policies section in the Community Standards. The Lion's Code, Student Conduct Code, Honor Code and Process, and information on many other policies are available from that link. You can find any and all other related data from the Office of Student Conduct & Community Responsibility web page. Also check the main Student Affairs Department Website.
Electronic Devices: Pretty easy — please turn off your cell phone ringer during class time. That's it for me! However…
The official LMU language for this is:
Please turn off and put out of sight all electronic devices (other than those and when allowed) during class-time. The interruptions and/or distractions they cause disrupt class and interfere with the learning process. Even if you are not on video, it's distracting to you.
Netiquette. Your instructor and fellow students need a safe, online learning environment. All opinions and experiences shared, no matter how controversial they may be perceived to be, must be respected in the spirit of academic discourse. You are encouraged to critique an idea but should not attack an individual. Working as a community of learners, we can build a respectful space for discourse. Below are some tips for good netiquette:
Students and faculty have a reasonable expectation for privacy in all learning spaces. Bimodal and remote learning can involve the use of synchronous video conferencing, asynchronous recorded lectures, live and online discussions, as well as online forums. In these venues, privacy is a priority for a safe learning environment. See Lion's code.
As a member of our online community, please follow these privacy guidelines:
Because of the nature of the class
delivery method during remote
zoom times we will
also take a look at a document which will serve as a guide for everyone in the class. This
Netiquette Document is published here
and on the Brightspace
site for this class. We will take a look at it during the first week of class and will work to make
it agreeable to everyone involved.
Public Safety can be reached 24/7/365 at 310.338.2893 [or x222 from a campus phone]. In a life-threatening emergency, call 911 first and then call Public Safety if possible. To report an incident, call Public Safety, submit an e-report on the Public Safety website or via the Rave Guardian mobile app, or visit Public Safety in Foley Annex. Review evacuation information and other safety tips posted in each learning space. Make sure you're registered to receive emergency alerts – confirm your contact information at lmu.edu/alert, and download Rave Guardian in the Apple or Google Play store. For more information and emergency preparedness tips, visit https://publicsafety.lmu.edu.To report an emergency or suspicious activity, contact the LMU Department of Public Safety by phone (x222 or 310-338-2893) or at the nearest emergency call box. In the event of an evacuation, follow the evacuation signage throughout the building to the designated safe refuge area where you will receive further instruction from Public Safety or a Building Captain.
For purposes of evacuating the building, our
safe area is the sunken gardens. There will be people
to guide you.
For more safety information and preparedness tips, visit http://www.lmu.edu/emergency.
Office hours are listed at the top of this syllabus page. I will make every effort to be available during
those hours, and if I cannot for some emergency reason, I'll make sure you all know about it in advance if
possible. Office hours, [due to the pandemic] will be held on zoom in my personal meeting room. A link to
office hours z'room is provided on the
BrightSpace course page.
I am also always available by e-mail at: my LMU mail address
There is a class slack channel on the LMUCS workspace, named
cmsi-284_spring2021. I post to that
channel with information at times, and it's a good place to ask/answer questions. It won't hurt you to
join! You can also DM me in that workspace.
Beginning in Fall 2020, the LMU CS department is trying a new communication method using Discord for our
virtual office hours, and as a virtual
Keck Lab environment. Feel free to join up there as well,
and post there with your colleagues in the department!
YOU MUST CHECK YOUR LION EMAIL ADDRESS OF RECORD. I will
start the semester's communications by sending all email blasts to everyone's
address, which is known as your address of record. If you specifically
provide me with a preferred alternative email to use I will be happy to oblige. I create a distribution
list to which I send all general communications in addition to the slack channel, so it is important for
me to have an email address which you will check on a regular basis.
If necessary, this syllabus and its contents are subject to revision. Students are responsible for any changes or modifications announced or distributed in class, emailed to students' LMU Lion accounts or posted on LMU's course management system, Brightspace. If you are absent from an in-person or online class meeting, it is your responsibility to check Brightspace [and/or the course website] and to check with the professor to see if you missed any important class announcements. Students should not rely on word-of-mouth from classmates.