Meeting Charleston
Today, I attended the Alumni Symposium. During freshman year, one of my classes had encouraged attendance to the (then in-person) symposium, but I was unable...
HW19: Chapter 23
23.6 Figure 23.14 shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs, and instead of taking 10 days, task T5 takes 40 days. Draw up new bar charts showing how the project might be reorganized.
This was a really interesting exercise. I used the template provided by this article to create a gantt bar chart/timeline. T5, the task we are extending, is only a dependency for one task. This task (T10) has another dependency (T9) that finishes after T5, even after its extension. Hence, I don’t think that this change actually impacts the timeline of the project much, if at all.
2021
Chapter 9
The journey does not end after a software project has gone live. This week’s reading was “Continuing the Journey” - Chapter 9 of Client-Centered Software Dev...
Chapter 6
“Databases reside at the heart of most software applications” (SD Chapter 6, pg 168). This week’s readings cover Chapter 6 of our textbook, Client-Centered S...
Chapter 5
This week’s reading (Chapter 5 of Client-Centered Software Development) covers domain classes and unit/system testing. According to the text, “domain classes...
Release early and often
Proper documentation for both internal and external users of a software application is crucial to its sustained success after deployment. This week, we read ...
Stupid or Solid?
This week, we read “From STUPID to Solid Code!” by William Durand. This article is packed with high-level do’s and dont’s of programming. The “dont’s” are co...
What’s Happening?
This week, our class chose and reflected on articles from Software, Computer, or CoACM magazines. While perusing software magazines (finding good ones was an...
This bugs me
6.4. Exercise - Find the Oldest Bug Find the oldest bug that’s still open in your chosen project. Write a blog entry describing the problem, with a theory ab...
Reflections on Open Source in Today’s World
This week, our assignment was to explore http://opensource.com/, reading at least two medium-length articles from the site and blogging about what we learned...
Reflections on FOSS
This class, CSCI 462, is centered around contributing to an open-source software project through bug fixes, documentation fixes, and other improvements. Befo...
Introduction
Hi everyone! My name is Janneke (pronounced ‘Yah-Nuh-Kuh’) Morin.
2020
HW21: Chapter 24
24.6 Explain why program inspections are an effective technique for discovering errors in a program. What types of error are unlikely to be discovered throug...
HW20: Team Progress II
I feel like our team made great progress on the most recent deliverable (deliverable 4)! We met via Zoom more often than we did between any other two variabl...
HW19: Chapter 23
23.6 Figure 23.14 shows the task durations for software project activities. Assume that a serious, unanticipated setback occurs, and instead of taking 10 day...
HW18: Chapter 21 and Chapter 22
21.4 Explain why an object-oriented approach to software development may not be suitable for real-time systems.
HW17: Team Progress I
This is my first reflection on our team’s testing project. I think this will be a helpful exercise as we move into the final stages of building our testing f...
HW16: Chapter 20
20.10 You work for a software company that has developed a system that provides information about consumers and that is used within a SoS by a number of othe...
HW15: Chapter 19
19.3 Why is it impossible to infer the emergent properties of a complex system from the properties of the system components? In the words of Ian Sommerville,...
HW14: Chapter 18
18.4 Define an interface specification for the Currency Converter and Check Credit Ratings services shown in Figure 18.7.
HW13: Chapter 17
17.10 Your company wishes to move from using desktop applications to accessing the same functionality remotely as services. Identify three risks that might a...
HW12: Chapter 16
16.9 Design the interfaces of components that might be used in a system for an emergency control room. You should design interfaces for a call-logging compon...
HW11: Chapter 9
9.8 Briefly describe the three main types of software maintenance. Why is it sometimes difficult to distinguish between them? Fault repairs to fix bugs and v...
HW10: Chapter 15
15.10 The reuse of software raises a number of copyright and intellectual property issues. If a customer pays the software contractor to develop a system, wh...
HW9: Chapter 8 and reflections on testing
8.7: Write a scenario that could be used to help design tests for the wilderness weather station system. Context: According to Chapter 7, Design and Implemen...
HW8: Mythical Man Month
Mythical Man-Month - Does adding more labor to a project linearly reduce the time to completion? Or does it do the opposite, particularly to an already late ...
HW7: Chapter 5 and 6
5.3: You have been asked to develop a system that will help with planning large-scale events and parties such as weddings, graduation celebrations, and birth...
HW6: Chapter 2
2.1 Suggest the most appropriate generic software process model that might be used as a basis for managing the development of the following systems. Explain ...
HW5: Chapter 4 and reflections
4.5: Using the technique suggested here, where natural language descriptions are presented in a standard format, write plausible user requirements for the fo...
HW4: Reflections on software failures
Our readings this week began with a focus on several software engineering failures which resulted in devastating incidents such as plane crashes (Space Craft...
HW3: Chapters 11 & 12
11.4: What is the common characteristic of all architectural styles that are geared to supporting software fault tolerance? Architectural styles geared to su...
HW2: Reflections on software engineering practices
The Complexity of Software and Its Evolution Software is, by definition, complex. Frederick P. Brooks, in his article “Essence and Accidents of Software Engi...
HW1: Chapter 1
1.3: What are the four important attributes that all professional software should possess? Suggest four other attributes that may sometimes be significant.
HW0: Introduction
Hi everyone! My name is Janneke (pronounced ‘Yah-Nuh-Kuh’) Morin.