A lot has happened since last Friday. (I think that's how I should always start my journals). On Sunday our small team of Felipe, Hubert, Kevin, and me met again; Felipe
inked out the mock-ups we created very nicely, and we thought of more ideas for Authoring content.
On Monday I didn't attend class (I have Elec 493 on Mondays at 1; I have to take it to graduate, so I have to show up there occasionally). This evidently was a bad choice, as the rest of the class took advantage of my absence and appointed me
the leader of a few very important aspects. I'm the Code Master, so (once I figure out how to actually work with branches in VS's source control) no one will be allowed to check into the main branch except for me and Brad. I'm also the leader of the Backend team, which right now means I'm the largest obstacle in the path of our workflow.
(Remember that being the one who is responsible does not necessarily imply either that you are the roadblock or that you have to be doing all the work yourself. -- SW)We need to get the interface that everyone will use ironed out (or at least sorta cobbled together) so that everyone else can start programming against it. Brad says (and I agree) that this is more or less a one- or two-person job, so I have work to do.
I'd be interested to know why this must be the case. If I were you, I would reconsider consenting to becoming the single point of failure for one of the most important aspects of the project...especially if it necessitates your "cobbling". --Chelsea As was pointed out in Brad's journal, is it best to make only one or two people responsible for the interfaces? Not only do you have the reasons Chelsea pointed out above, but also, this leaves 11 people in the dark about the workings of something they will be dealing with for the rest of the semester.
Fortunately, I have made substantial progress towards that. I created the class's Solution in the repository and created projects for the Backend's code. I created a simple, temporary interface for interacting with a couple of the data objects (IEntity and IContent... a link to documentation when I have time to write one :-)) that actually interacts with the Atelier database that I created in our SQL Server. I also made the DB more secure than *ahem* other Comp 410 classes have done, as I created a "comp410" user to access the database, and I'm not using the general Sql Server superuser. Also, I'm storing the username and password in the registry, not the web.config file. I feel good about these achievements, since I've never created databases before, and I've never worked with the registry before. I also
created a coding standards document as I was doing this.
We also had
our second customer meeting on Thursday. I was quite amazed that Mr. Scanlon had remembered all of our names. This meeting went smoother than the previous one. I think that he didn't want to bias our opinions of how to design the system the first time, and was quite reluctant to actually give us necessary information, but today's focus was on us presenting him our initial ideas, and thus his role was to redirect our momentum if he found it to be improper, rather than to push us off.